json-schema-to-elm
json-schema-to-elm copied to clipboard
Generates Elm types, JSON decoders, JSON encoders and fuzz tests from JSON schema specifications
Investigate whether it makes sense to support the 'default' keyword, see 7.3 in the [validation spec](http://json-schema.org/latest/json-schema-validation.html#rfc.section.7.3).
Also while looking at enums: remove the `"type": "string"` constraint, if possible.
See http://json-schema.org/latest/json-schema-validation.html#format For example, if we have the node ``` "datum": { "required: ["createdDate"] "properties": { "createdDate": { "type": "string", "format": "date-time" } } } ``` we want it to...
Investigate whether there is a reasonable type+parser+decoder that can be generated from the generic types: ``` { "type": "object" } ``` and ``` { "type": "array" } ``` i.e. maybe...
Entries of type `string` can get a `pattern`, restricting the value space. Arguably, the generated Elm code should prevent invalid JSON from being created, so it'd have to verify that...
As far as I can tell, there is currently no support for `patternProperties`, arguably one of the more useful features of JSON schema. Here is how I'd imagine to map...
Currently, we don't recognise subschemas which may contain both a `"definitions"` property and a `"type"` property. The current assumption is that all definitions are contained in the `"definitions"` property of...
''' /usr/local/bin/js2e /Users/marcpawl/github/Triumph_TTS/fake_meshwesh/json_schemas --module-name Meshwesh warning: :logger :level has been set to :warn in config files, please use :warning instead (logger 1.15.5) lib/logger/app.ex:102: Logger.App.default_level/0 (logger 1.15.5) lib/logger/app.ex:35: Logger.App.start/2 (kernel 9.0.2)...
* fix: handle anonymous name * fix: handle object has no properties * chore: update to elixir 1.16 and fix related warnings closes #180