-
Notifications
You must be signed in to change notification settings - Fork 334
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
Add option to export raw JSON Schema files #1476
Comments
How are those individual JSON schemas used? The user has to manually move them somewhere anyways, right? What if we generate them by default (maybe to a sub-folder) and then the user can choose to use or ignore them. I would like to avoid the library code trying to make assumtions on how the binary it is called from works (as noted in #1478). |
As far as I understand, if someone needs to write e.g. an execute msg by hand, they take the
I'd be okay with that |
Thanks to @hashedone for pointing this out. Apparently raw JSON schema (without our custom metadata and structure) files are useful for IDEs - they help people write valid JSON msgs by hand.
The text was updated successfully, but these errors were encountered: