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.

Sign up for GitHub

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

Jump to bottom

Add a mechanism for evolving JSON Schema drafts to add keywords #24

Open
Julian opened this issue Feb 19, 2023 · 0 comments
Open

Add a mechanism for evolving JSON Schema drafts to add keywords #24

Julian opened this issue Feb 19, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@Julian
Copy link
Member

Julian commented Feb 19, 2023 •
edited
Loading

We need some generic mechanism for saying "I have a new Specification, it's like DRAFT202012 but with a new keyword foo" and then allowing the new keyword foo to either have a schema value (a la additionalItems or whatever) or schema-containing values (properties) etc...

Obviously the most "generic" mechanism will be fully defining subresources_of (and now maybe_in_subresource) as a generic callable -- but a simple/fast interface which just allows adding the extra keyword will make things easier downstream.
@Julian Julian added the enhancement New feature or request label Feb 19, 2023
Julian added a commit that referenced this issue Feb 19, 2023
@Julian
Better handle traversing into subresources while resolving pointers.
9835d62 
This is .. ugly and duplicative. But more correct.

When traversing a JSON Pointer, we need to know when and if we're
entering a subresource, and this differs by spec (and has to do
with whether we've just entered a known keyword).

This will likely get less duplicative when #24 is done.
@Julian Julian mentioned this issue Feb 22, 2023
Closed
@Julian Julian modified the milestone: v1.0 Feb 26, 2023
@Julian Julian mentioned this issue Mar 20, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Julian