v0.6.0 [2026-08-17]
Changed
- Bumped the elixir version from 1.14 to 1.20 and.
Fixed
- Fixed all compiler, credo and dialyzer warnings.
v0.5.0 [2023-03-26]
Added
- Now supports the
defaultkeyword for each schema node type. - Now supports boolean values for the
additionalPropertieskeyword.
Changed
- When defining an anonymous type using the
itemskeyword, it is now named:anonymousrather thanitemsin the parsed document.
Fixed
- Fixed a bug where the parser would throw an unexpected error if the
itemsproperty contained a primitive type.
v0.4.0 [2022-05-09]
Changed
- Replaces auto-generated schema names like
zeroandonewith:anonymousmaking it easier for a consuming project to decide what to do when a subschema does not have an explicit name. (#97) - Replaces stringly-typed
typeproperties for several schema types to instead use specific atoms corresponding to the set of valid JSON value type. - Adds better error description for invalid
uniontypes.
v0.3.0 [2019-10-30]
Added
- Support for the generic
descriptionkeyword (#14). - support for the
constkeyword (#21).
Fixed
- Various bugs related to parsing nested root object (#35).
v0.2.0 [2019-03-24]
Added
- Support for parsing the following JSON schema types:
additionalProperties, andpatternProperties.
Changed
- Replaced the
TypePathtype wih theURItype when specifying local paths in a JSON schema document.
v0.1.0 [2018-07-27]
NOTE: This initial release is a fork of https://github.com/dragonwasrobot/json-schema-to-elm, and so this version contains all existing changes made in that project. As a result, the parser and inspection logic found in this first version reflects which parts of the JSON Schema specification was needed in the original project.
Added
Support for parsing the following JSON schema types:
allOf,anyOf,array(keyworditemswhen value is a object),enum,object, (keywordproperties),oneOf,primitive(keywordtypeexcept forobjectandarray),tuple(keyworditemswhen value is a list of objects), andunion(keywordtypewhen value is a list of strings).
Parsing of the basic properties of a JSON schema document:
schema,$id,$ref,title,description,"definitions", andrequired.
Can resolve references, using
$ref, across different JSON schema files as long as they are parsed together.Prints human friendly error messages.