haskell/aeson

Use auto-formatting (hindent?)

Open

#527 opened on Mar 19, 2017

View on GitHubContributor guide
 (14 comments) (1 reaction) (0 assignees)Haskell (334 forks)batch import
blocked by upstream/should be done externallygood first issuehelp wanted

Repository metrics

Stars
 (1,298 stars)
PR merge metrics
 (Avg merge 935d 9h) (5 merged PRs in 30d)

Description

I think auto-formatting is a big win. hindent also formats very close to what I do personally anyway so I'm a big fan, but there are a lot of differences from the aeson style.

What do others think?

Contributor guide

Research direction
Review the existing code formatting in aeson, compare with hindent's output, and summarize the community consensus for or against using auto formatting.
Tech stack
haskell
Domain
backend
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80