@@ -2,6 +2,22 @@ For the latest version of this document, please see [https://github.com/bos/aeso
22
33#### WIP
44
5+* The operators for parsing fields now have named aliases:
6+ - `.:` => `parseField`
7+ - `.:?` => `parseFieldMaybe`
8+ - `.:!` => `parseFieldMaybe'`
9+ - These functions now also have variants with explicit parser functions: `explicitParseField`, `explicitParseFieldMaybe`, "explicitParseFieldMaybe'`
10+Thanks to Oleg Grenrus.
11+
12+* `ToJSONKey (Identity a)` and `FromJSONKey (Identity a)` no longer require the unnecessary `FromJSON a` constraint. Thanks to Oleg Grenrus.
13+
14+* Added `Data.Aeson.Encoding.pair'` which is a more general version of `Data.Aeson.Encoding.pair'`. Thanks to Andrew Martin.
15+
16+* `Day`s BCE are properly encoded, and `+` is now a valid prefix for other dates. Thanks to Matt Parsons.
17+
18+* Some commonly used ToJSON instances are now specialized in order to improve compile time. Thanks to Bartosz Nitka.
19+
20+
521[JSONTestSuite](https://github.com/nst/JSONTestSuite) cleanups, all
622motivated by tighter RFC 7159 compliance:
723
@@ -22,13 +38,10 @@ categorised as follows:
2238
2339* The parser does not (and will not) support UTF-16, UTF-32, or byte
2440 order marks (BOM).
25−
2641* The parser accepts unescaped control characters, even though the RFC
2742 states that control characters must be escaped. (This may change at
2843 some point, but doesn't seem important.)
2944
30−- Days BCE are properly encoded.
31−
3245#### 1.0.2.1
3346
3447* Fixes a regression where a bunch of valid characters caused an