json-spec 1.0.0.0 → 1.0.1.0

raw patch · 3 files changed

+19/−6 lines, 3 filesPVP ok

version bump matches the API change (PVP)

API changes (from Hackage documentation)

Files

• json-spec.cabal +1/−1
• src/Data/JsonSpec.hs +17/−4
• src/Data/JsonSpec/Spec.hs +1/−1

@@ -1,6 +1,6 @@ cabal-version:       3.0 name:                json-spec-version:             1.0.0.0+version:             1.0.1.0 synopsis:            Type-level JSON specification maintainer:          rick@owensmurray.com description:         See the README at: https://github.com/owensmurray/json-spec#json-spec

@@ -68,21 +68,34 @@  -} module Data.JsonSpec (+  -- * Writing specifications   Specification(..),+  (:::),+  (::?),+  FieldSpec(..),++  -- * Encoding/decoding via a Specification   HasJsonEncodingSpec(..),   HasJsonDecodingSpec(..),   SpecJSON(..),   Tag(..),   Field(..),   unField,-  JSONStructure,   Ref(..),++  -- * Direct encoding/decoding   eitherDecode,   encode,++  -- * Other stuff+  {-|+    The items in this section are mainly exported because once in a+    while you might need to include them in a type signature, but they+    are not intended to be used directly.+  -}+  JSONStructure,   StructureFromJSON,-  FieldSpec(..),-  (:::),-  (::?),+  StructureToJSON, ) where  

@@ -285,7 +285,7 @@   @EncodingSpec Foo@, which would expand strictly... to infinity.    Using `JsonLet` prevents the specification type from being infinitely-  sized, but what about "structure" type which holds real values+  sized, but what about the "structure" type which holds real values   corresponding to the spec? The structure type has to have some way to   reference itself or else it too would be infinitely sized.