json-schema changelog

Changelog History

Page 2

• v0.7.3.0 Changes

  • ➕ Add JSONSchema instances for all standard Num types and Scientific.

• v0.7.2.0 Changes

  • ➕ Add JSONSchema instances for Double, Float, Fixed

• v0.7.1.1 Changes

  • 👍 Allow generic-deriving 1.7.*

• v0.7.1.0 Changes

  • Export GJSONSchema type to allow clients to write type signatures for gSchema and gSchemaWithSettings.

• v0.7.0.2 Changes

  • 👍 Allow time 1.5.*

• v0.7.0.1 Changes

  • ⬇️ Drop support for old tasty versions

• v0.7.0.0 Changes

  • ✂ Removed the Null constructor from Schema, use Data.JSON.Schema.Combinators.nullable instead.

  • ➕ Added the Validation module that can be used to validate a json object against a schema and to get descriptive error messages.

  • ⚡️ Updates for Maybe fixes in generic-aeson 0.2.0.0 including more thorough test cases.

• v0.6.1 Changes

  • ➕ Add JSONSchema instances for tuples up to length 15 (matching aeson 0.8 instances)
  • Specify uniqueness for JSONSchema instances for Set.

• v0.6.1.1 Changes

  • 🛠 Bugfix: Remove underscores from fields and constructors in generated schemas to match generic-aeson.

• v0.6 Changes

  💥 Breaking changes:

  • ➕ Add Constant Aeson.Value type to Schema
  • 🔄 Change Number to take a Bound for the boundary. Before this the upper bound could not be -1.
  • 🔄 Change Value and Array to take a LengthBound. The difference from Number is that these values should always be >= 0 if present.

  Minor:

  • ➕ Add Bound { lower :: Maybe Int, upper :: Maybe Int }
  • ➕ Add unbounded as a shorthand for a Bound without restrictions
  • ➕ Add LengthBound { lowerLength :: Maybe Int, upperLength :: Maybe Int }
  • ➕ Add unboundedLength as a shorthand for a LengthBound without restrictions
  • ➕ Add remaining JSONSchema instances based on existing Aeson instances. UTCTime, Set, Lazy Text, and tuples up to length 7.
  • ➕ Add enum combinator as a shorthand for creating a Choice of Constants

• « First
• ‹ Prev
• 1
• 2
• 3
• Next ›
• Last »