Add basic JSON schema validation #18
Merged
Conversation
This file contains 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
This schema is incomplete and inaccurate
This ID is completely made up... but should be unique
Fix some types and add example documentation for `a_galaxy_workflow` property
|
super cool!! |
|
Thank you @wm75! that would be awesome! I'll merge this now, and hopefully, get the other schema-based features (documentation on hover and auto-completion suggestions) in a follow-up soon. |
6 tasks
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.
This PR adds a basic schema validation for Galaxy Native Workflows (.ga)
I couldn't find an existing JSON schema for .ga workflows, so a really basic, incomplete, and undocumented JSON schema has been added to the project here. The extension will now validate all .ga files using this schema and should be easy to provide additional schema-based features like hover documentation and autocompletion suggestions in future PRs.
Extending and documenting the schema further should be also pretty easy by following the documentation any help with that will be much appreciated :)