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
Since there is now a JSON schema (#793) would be great to have it mapped to goss.yml files via Schema Store. This would mean that folks using editor plugins like https://github.com/redhat-developer/vscode-yaml would immediately get validation for their goss files.
@lox for my own clarity, it seems the actual PR would be to the schemastore repo, not Goss, correct? Or is there something needed to be also done here.
thanks @aelsabbahy ! I'll try updating the json schema against https://github.com/goss-org/goss/releases/tag/v0.4.0-rc.1 and propose a unit tests for future regressions in goss-org/goss, either this week or more likely early September when I some available time. Anyone feel free to tackle this earlier if some bandwidth is available earlier. After that, we can get a PR on schemastore, possibly versioned if there is need to account for breaking changes in syntax in 0.4
Describe the feature:
Since there is now a JSON schema (#793) would be great to have it mapped to goss.yml files via Schema Store. This would mean that folks using editor plugins like https://github.com/redhat-developer/vscode-yaml would immediately get validation for their goss files.
Describe the solution you'd like
Reference the JSON Schema via https://github.com/SchemaStore/schemastore/blob/master/CONTRIBUTING.md#catalog (happy to do this if there is interest)
Describe alternatives you've considered
Manual editor configuration.
The text was updated successfully, but these errors were encountered: