add detail on parse error location and cause #221
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added an instance for the 'Fixed' class.
parseJSON for the variations on ISO-8601 dates as listed in ECMA-262.
Add functions for inspecting Values
Added eitherDecode and eitherDecode'
Add elaborate guide to Data.Aeson's Haddock documentation
De-emphasize working directly with the Value type as this is not the common (or recommended) way to use the library, but still include documentation on how to use it when it's called for. Since the documentation on using generics is documented in the FromJSON and ToJSON classes, refer to that documentation instead of only documenting one method (which is not the preferred method anymore with default signatures I believe).
Improve introductionary documentation
--HG-- extra : amend_source : d48e612e53488f41b0d6f2ceb4395978b48d411d
--HG-- extra : amend_source : aa3ad961a2c62e2948ee0e213615c01ac002b42c
This is more portable between compilers as well as between variants on GHC (ex: HaLVM is building off of head so GHC appears as 7.8.3 while TH is 2.10).
Data.Aeson.Types.Instances: fix UTCTime for years outside of [0, 9999]
Modernizing the TH example.
Export 'camelTo' function and fix its tests
Currently, eitherDecodeWith drops the attoparsec context when returning a Left value. In box/attoparsec#79, the context is included in the output of L.eitherResult. Since L.parseOnly does not exist, the closest we can get to the structure of eitherDecodeStrictWith here in aeson is L.eitherResult . L.parse.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This obsoletes #210.
See also #220, haskell/attoparsec#79.