Repository navigation
Conversation
json schema
This was referenced Oct 22, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Towards #74, this gives a schema for the "standard" formats. Two things:
customones go or how they interact with the other keys or where thecustom-keyed schema goes. It might make sense to make it a separate schema but not sure?$schemawhich is more of a convention but still could be useful at some point.draftsas well? I am not totally clear how a "build" would work with the schema, which I think should be for public consumption by other readers/writersSorry if you had already started this @willow-ahrens but I didn't see any branches here or the like and you don't seem to have a fork.