ChangeLog.devel

1.3.6

• Add abilities to pre-register schemas with URIs into JsonSchemaFactory.
• The default schema is now draft v3 hyper-schema (instead of the core schema).

1.3.5

• Dependencies update (including TestNG).
• Implement numeric value equality while preserving numeric type (ie, 1.0 is equal to 1 but the first is a number while the second is an integer).
• Draft v3 hyperschema syntax checking.

1.3.4

• jackson-databind dependency update (2.0.6 -> 2.1.1).
• Conform to JSON Schema equality for numeric instances.
• Syntax validator API change.
• User visible change: node type null appears before number in relevant syntax/validation messages.
• More Javadoc updates

1.3.3

• Major user API changes in JsonSchemaFactory.
• Complete examples in package org.eel.kitchen.jsonschema.examples.
• FormatAttribute has lost its ValidationContext argument, which was unused.
• Bring back draft v3 format attributes into the mix (except for color and style, which are still not supported).
• Rewrite all format attributes/syntax checkers/keyword validator tests.
• Major javadoc updates.

1.3.2

• KeywordBundle has disappeared, replaced with KeywordRegistry.
• Implement all draft v4 proposed keywords.
• Override Jackson's JsonNodeFactory so that DecimalNode instances are built with .stripTrailingZeros(), see https://github.com/FasterXML/jackson-databind/issues/80.
• The default JsonSchemaFactory instance has now support for both draft v3 and draft v4.

1.3.1

• Some internal code cleanup.
• Implement inner schema addressing mode by splitting SchemaContainer in two classes.
• Make AddressingMode build SchemaContainer instances.
• IdFragment is dead, replaced with IllegalFragment.
• Start a SchemaBundle implementation, inject it into a SchemaRegistry. Use that in test code only for now.

1.3.0

• Remove deprecated methods.
• Update reference to JSON Pointer and JSON Reference drafts.
• Fix format bundle bug (declared but not actually used. Meh.).
• Start API changes to support inner schema addressing: SchemaContainer now takes care of .contains() and .resolve() methods when processing JSON References.
• Move some classes to a dedicated schema package.
• More tests; more fatal errors implemented and tested.