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

Add option to export raw JSON Schema files #1476

Closed
uint opened this issue Nov 7, 2022 · 2 comments · Fixed by #1478
Closed

Add option to export raw JSON Schema files #1476

uint opened this issue Nov 7, 2022 · 2 comments · Fixed by #1478
Assignees
Labels
schema cosmwasm-schema crate
Milestone

Comments

@uint
Copy link
Contributor

uint commented Nov 7, 2022

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.

@uint uint added the schema cosmwasm-schema crate label Nov 7, 2022
@uint uint self-assigned this Nov 7, 2022
@webmaster128
Copy link
Member

webmaster128 commented Nov 15, 2022

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).

@uint
Copy link
Contributor Author

uint commented Nov 15, 2022

How are those individual JSON schemas used?

As far as I understand, if someone needs to write e.g. an execute msg by hand, they take the ExecuteMsg schema, put that in their IDE, and then their IDE helps them write the msg correctly.

What if we generate them by default (maybe to a sub-folder)

I'd be okay with that

@webmaster128 webmaster128 added this to the 1.2.0 milestone Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
schema cosmwasm-schema crate
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants