git.iko.soy/typeable/aeson
on 0.9.x help sign in
typeable/aeson/changelog.md
176 lines 5.6 kB history raw
10.9.0.1
3* A stray export of encodeToBuilder got away!
50.9.0.0
7* The json and json' parsers are now synonyms for value and value', in
8 conformance with the looser semantics of RFC 7159.
10* Renamed encodeToByteStringBuilder to the more compact
11 encodeToBuilder.
130.8.1.1
15* The dependency on the unordered-containers package was too lax, and
16 has been corrected.
180.8.1.0
20* Encoding a Scientific value with a huge exponent is now handled
21 efficiently. (This would previously allocate a huge
22 arbitrary-precision integer, potentially leading to a denial of
23 service.)
25* Handling of strings that contain backslash escape sequences is
26 greatly improved. For a pathological string containing almost a
27 megabyte of consecutive backslashes, the new implementation is 27x
28 faster and uses 42x less memory.
30* The ToJSON instance for UTCTime is rendered with higher (picosecond)
31 resolution.
33* The value parser now correctly handles leading whitespace.
35* New instances of ToJSON and FromJSON for Data.Sequence and
36 Data.Functor.Identity. The Value type now has a Read instance.
38* ZonedTime parser ordering now favours the standard JSON format,
39 increasing efficiency in the common case.
41* Encoding to a Text.Builder now escapes '<' and '>' characters, to
42 reduce XSS risk.
440.8.0.2
46* Fix ToJSON instance for 15-tuples (see #223).
480.8.0.1
50* Support time-1.5.
520.8.0.0
54* Add ToJSON and FromJSON instances for tuples of up to 15 elements.
560.7.1.0
58* Major compiler and library compatibility changes: we have dropped
59 support for GHC older than 7.4, text older than 1.1, and bytestring
60 older than 0.10.4.0. Supporting the older versions had become
61 increasingly difficult, to the point where it was no longer worth
62 it.
640.7.0.0
66* The performance of encoding to and decoding of bytestrings have both
67 improved by up to 2x, while also using less memory.
69* New dependency: the scientific package lets us parse floating point
70 numbers more quickly and accurately.
72* eitherDecode, decodeStrictWith: fixed bugs.
74* Added FromJSON and ToJSON instances for Tree and Scientific.
76* Fixed the ToJSON instances for UTCTime and ZonedTime.
780.6 series
80* Much improved documentation.
82* Angle brackets are now escaped in JSON strings, to help avoid XSS
83 attacks.
85* Fixed up handling of nullary constructors when using generic
86 encoding.
88* Added ToJSON/FromJSON instances for:
90 * The Fixed class
91 * ISO-8601 dates: UTCTime, ZonedTime, and TimeZone
93* Added accessor functions for inspecting Values.
95* Added eitherDecode function that returns an error message if
96 decoding fails.
980.5 to 0.6
100* This release introduces a slightly obscure, but
101 backwards-incompatible, change.
103 In the generic APIs of versions 0.4 and 0.5, fields whose names
104 began with a "_" character would have this character removed. This
105 no longer occurs, as it was both buggy and surprising
106 (https://github.com/bos/aeson/issues/53).
108* Fixed a bug in generic decoding of nullary constructors
109 (https://github.com/bos/aeson/issues/62).
1110.4 to 0.5
113* When used with the UTF-8 encoding performance improvements
114 introduced in version 0.11.1.12 of the text package, this release
115 improves aeson's JSON encoding performance by 33% relative to aeson
116 0.4.
118 As part of achieving this improvement, an API change was necessary.
119 The fromValue function in the Data.Aeson.Encode module now uses the
120 text package's Builder type instead of the blaze-builder package's
121 Builder type.
1230.3 to 0.4
125* The new decode function complements the longstanding encode
126 function, and makes the API simpler.
128* New examples make it easier to learn to use the package
129 (https://github.com/bos/aeson/tree/master/examples).
131* Generics support
133 aeson's support for data-type generic programming makes it possible
134 to use JSON encodings of most data types without writing any
135 boilerplate instances.
137 Thanks to Bas Van Dijk, aeson now supports the two major schemes for
138 doing datatype-generic programming:
140 * the modern mechanism, built into GHC itself
141 (http://www.haskell.org/ghc/docs/latest/html/users_guide/generic-programming.html)
143 * the older mechanism, based on SYB (aka "scrap your
144 boilerplate")
146 The modern GHC-based generic mechanism is fast and terse: in fact,
147 its performance is generally comparable in performance to
148 hand-written and TH-derived ToJSON and FromJSON instances. To see
149 how to use GHC generics, refer to examples/Generic.hs.
151 The SYB-based generics support lives in Data.Aeson.Generic and is
152 provided mainly for users of GHC older than 7.2. SYB is far slower
153 (by about 10x) than the more modern generic mechanism. To see how
154 to use SYB generics, refer to examples/GenericSYB.hs.
156* We switched the intermediate representation of JSON objects from
157 Data.Map to Data.HashMap which has improved type conversion
158 performance.
160* Instances of ToJSON and FromJSON for tuples are between 45% and 70%
161 faster than in 0.3.
163* Evaluation control
165 This version of aeson makes explicit the decoupling between
166 *identifying* an element of a JSON document and *converting* it to
167 Haskell. See the Data.Aeson.Parser documentation for details.
169 The normal aeson decode function performs identification strictly,
170 but defers conversion until needed. This can result in improved
171 performance (e.g. if the results of some conversions are never
172 needed), but at a cost in increased memory consumption.
174 The new decode' function performs identification and conversion
175 immediately. This incurs an up-front cost in CPU cycles, but
176 reduces reduce memory consumption.