-
Notifications
You must be signed in to change notification settings - Fork 484
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement JSON schema field constraints #215
Comments
Here are some examples of integer range constraints expressed as regular expressions: https://stackoverflow.com/a/34680927/3006474, https://3widgets.com/ |
What is the status of this? Are length of tuples/lists also implemented? |
To be honest I switched to ggml’s ebnf for grammar constraints. |
How does an EBNF-specified grammar provide these constraints? |
While playing around trying to validate meta schemas, I ran into
|
Regarding recursion, there's an existing issue for that (albeit framed via the Pydantic interface): #330. Feel free to continue the discussion there. |
We can specify constraints for the different fields in the JSON schema specification. Only
maxLength
for strings is currently implemented. Remaining:Strings
minLength
pattern
and the default formats that can be specified via the
format
keyword:date-time
time
date
duration
email
idn-email
hostname
idn-hostname
ipv4
ipv6
uuid
uri
uri-reference
iri
iri-reference
uri-template
regex
Numeric types
multipleOf
minimum
exclusiveMinimum
maximum
exclusiveMaximum
Arrays
minItems
maxItems
(may only be applicable dynamically)uniqueItems
Tuples
See https://json-schema.org/understanding-json-schema/reference/array#tupleValidation
Required fields
We should handle optional fields as well, i.e. those not specified in the
required
field of the schema.The text was updated successfully, but these errors were encountered: