schematic
schematic copied to clipboard
type-safe JSON spec and validation tool
It would be better to encode an optional field as "not being required", then begin "one of: null and value"
I apologize for doing this. I'm no longer interested in JSON Schema, and `hjsonschema`'s serious flaws mean I don't want to recommend it to anyone anymore. You can read more...
Assuming we have such a type ```haskell type SomeCode = SchemaText '[TRegex "^[0-9A-ZА-Я]{2}$"] ``` but the result scheme looks like ```json "items": { "pattern": "^[0-9A-ZÐ-Я]{2}$", "type": "string" } ``` Looks...
Add validation for Union. Also some code-cleaning to pedantic compiling.
I didn't check it yet...
The main changes: - using type parameters to demote types transparently - compile cycle was removed - support for ghc from 8.2 to 8.6 (lts-10.0 - lts 13.7)
Release 0.4.3.0 on [Hackage](https://hackage.haskell.org/package/schematic)
Currently regular expressions (`TRegex` for `SchemaText`) get compiled only when (and if) relevant data being validated at run-time. Thus even malformed regexes pass compilation and might sleep past testing. It...
Help needed