medea icon indicating copy to clipboard operation
medea copied to clipboard

A JSON schema language

Results 10 medea issues
Sort by recently updated
recently updated
newest added

when a property is missing from an object, for example, the whole JSON structure is returned without any specific mismatch information under the error 'NotOneOfOptions' this makes debugging a schema...

Decimal, Integer, BigInt support please!

Would be great to automate the schema creation - even if it's crude at first, as a developer tool. Admittedly, in many cases this may be an anti-pattern, however it...

it would be useful to have higher order types defined which can be supplied with a parameter, such as: ``` $schema wrapper $type $object $property-name "tag" $property-schema $string $property-name "contents"...

would be great to have an `$include` syntax, in the form: `$include as x` - to import the Start schema in that file as an an available schema under name...

in addition to the `string-values` options, there ought to be regex support for the definition of dates, phone numbers, emails, etc.

After working with Medea, we find that we cannot express the following usecase: IF tag = "OrderAddress" THEN dbObject must use a single specified schema (out of 9 possible types)

enhancement

this should be `InvalidJson Provided`

bug
documentation

for parseErrors we should be re-exporting `errorBundlePretty` at minimum.

bug
documentation

lets add a line-comment syntax with `#`

enhancement