You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are multiple times when we (the JSON Schema team) would like to be able to validate JSON embedded in other files, such as markdown. (Specifically, JSON Schema examples in our docs and website.)
I imagine it would work by allowing the following:
Specify what files should be inspected
Identify which fragments of the files are JSON (This may need different approaches per format, potentially with a way to self declare the wish to be validated)
Process such fragments which self-identify which Schema they should be validated with (such as a standard meta-schema)
Optionally take an argument/s which specifies a default JSON Schema to be used for all fragments within a given file/glob of files
Please do reach out to me on Slack or @Julian. I likely won't see follow up comments here directly as I've declared GH notificaiton bankruptcy. Thanks.
The text was updated successfully, but these errors were encountered:
Okay, cool! This sounds super interesting but also non-trivial.
I likely won't see follow up comments here directly as I've declared GH notificaiton bankruptcy.
I understand, but also this is kind of unfortunate since I've moved in the opposite direction, turning off the email notifications and using the github.com/notifications page to manage a lot of my open source work queue. I'll reach out via another means after I have time to digest this and think about good interfaces for expressing these ideas in the CLI.
There are multiple times when we (the JSON Schema team) would like to be able to validate JSON embedded in other files, such as markdown. (Specifically, JSON Schema examples in our docs and website.)
I imagine it would work by allowing the following:
Please do reach out to me on Slack or @Julian. I likely won't see follow up comments here directly as I've declared GH notificaiton bankruptcy. Thanks.
The text was updated successfully, but these errors were encountered: