Skip to content
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

encoding/jsonschema: implement more format constraints #3479

Open
rogpeppe opened this issue Oct 3, 2024 · 0 comments
Open

encoding/jsonschema: implement more format constraints #3479

rogpeppe opened this issue Oct 3, 2024 · 0 comments

Comments

@rogpeppe
Copy link
Member

rogpeppe commented Oct 3, 2024

The format keyword in jsonschema could be implemented more fully.

As a very rough guide to prioritization, here are the set of formats used in schemastore.org,
each with the count of how many schemas use that keyword (ignoring different versions
of the same schema):

82   uri
26   date-time
20   uri-reference
14   regex
12   email
7    date
3    uuid
2    hostname
1    time
1    iri
1    ipv6
1    ipv4
1    int64
1    int32
1    duration
1    double
1    byte

Note that some of the formats used above are not actually recognized in JSON Schema. For example, int32 and int64 are OpenAPI-specific.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant