3Changes that affect users of aeson should be mentioned in `changelog.md`. It should contain
5* The level of change, see [PVP](https://wiki.haskell.org/Package_versioning_policy)
7 * How to migrate existing code
8 * When it should be used
11Add this entry under an `## Upcoming` header above existing releases.
13The exact format of entries is not important as we'll go through everything before a release is made.
21* One pragma on each line
23* Sort lexicographically
26{-# LANGUAGE BangPatterns #-}
28{-# LANGUAGE DataKinds #-}
31## Module declaration and exports
33* Opening paren on its own line
38module Data.Aeson.Types.ToJSON
40 -- * Core JSON classes
42 -- * Liftings to unary and binary type constructors
50* No alignment of import lists or qualifications
51* Sort lexicographically (qualified imports will be last)
52* No space between types and constructor lists
53* Sort identifiers in import lists lexicographically
56import BarBar as B ((<>), foo)
keysesc to close
- j k
- move down, up
- enter
- open
- esc
- back, or up a level
- 1 2 3 4
- readme, files, commits, refs
- /
- filter
- y
- copy the clone command
- c
- compare the chosen commit with another (or shift-click both)
- ?
- show or hide this list