autodocodec-exact 0.0.0.2 → 0.0.1.0
raw patch · 4 files changed
+13/−1 lines, 4 filessetup-changedPVP ok
version bump matches the API change (PVP)
API changes (from Hackage documentation)
+ Autodocodec.Exact: ExactParseErrorBimapFailure :: !String -> ExactParseErrorMessage
+ Autodocodec.Exact: ExactParseErrorDisjointBothFailed :: !ExactParseError -> !ExactParseError -> ExactParseErrorMessage
+ Autodocodec.Exact: ExactParseErrorDisjointBothSucceeded :: ExactParseErrorMessage
+ Autodocodec.Exact: ExactParseErrorExactMatch :: !String -> !String -> ExactParseErrorMessage
+ Autodocodec.Exact: ExactParseErrorIntegerOutOfBounds :: !Bounds Integer -> !Integer -> !String -> ExactParseErrorMessage
+ Autodocodec.Exact: ExactParseErrorKeyParseError :: !Key -> !String -> ExactParseErrorMessage
+ Autodocodec.Exact: ExactParseErrorMissingDiscriminator :: !Key -> !Object -> ExactParseErrorMessage
+ Autodocodec.Exact: ExactParseErrorMissingRequiredKey :: !Key -> !Object -> ExactParseErrorMessage
+ Autodocodec.Exact: ExactParseErrorNumberOutOfBounds :: !Bounds Scientific -> !Scientific -> !String -> ExactParseErrorMessage
+ Autodocodec.Exact: ExactParseErrorPossiblyJointBothFailed :: !ExactParseError -> !ExactParseError -> ExactParseErrorMessage
+ Autodocodec.Exact: ExactParseErrorStringOutOfBounds :: !StringBounds -> !Text -> !String -> ExactParseErrorMessage
+ Autodocodec.Exact: ExactParseErrorTypeMismatch :: !String -> !Value -> ExactParseErrorMessage
+ Autodocodec.Exact: ExactParseErrorUnknownDiscriminator :: !Text -> !Object -> ExactParseErrorMessage
+ Autodocodec.Exact: ExactParseErrorUnsafeNumber :: !Bounds Scientific -> !Scientific -> !String -> ExactParseErrorMessage
+ Autodocodec.Exact: data ExactParseErrorMessage
Files
- CHANGELOG.md +8/−0
- Setup.hs +2/−0
- autodocodec-exact.cabal +2/−1
- src/Autodocodec/Exact.hs +1/−0
CHANGELOG.md view
@@ -1,5 +1,13 @@ # Changelog +## [0.0.1.0] - 2026-10-07++### Added++* `ExactParseErrorMessage` and its constructors are now exported.+ `ExactParseError` already exposed the field that holds one, so there was no+ way to look at a parse error without them.+ ## [0.0.0.2] - 2026-07-14 ### Changed
+ Setup.hs view
@@ -0,0 +1,2 @@+import Distribution.Simple+main = defaultMain
autodocodec-exact.cabal view
@@ -5,7 +5,7 @@ -- see: https://github.com/sol/hpack name: autodocodec-exact-version: 0.0.0.2+version: 0.0.1.0 synopsis: Exact decoder for autodocodec homepage: https://github.com/NorfairKing/autodocodec#readme bug-reports: https://github.com/NorfairKing/autodocodec/issues@@ -30,6 +30,7 @@ Paths_autodocodec_exact hs-source-dirs: src+ ghc-options: -Wall -Wincomplete-uni-patterns -Wincomplete-record-updates -Wpartial-fields -Widentities -Wredundant-constraints -Wcpp-undef build-depends: aeson , aeson-pretty
src/Autodocodec/Exact.hs view
@@ -27,6 +27,7 @@ parseExactJSONObjectVia, -- ExactParseError (..),+ ExactParseErrorMessage (..), prettyExactParseError, ExactParseWarning (..), prettyExactParseWarning,