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
Only actual rattler-build YAML files get validated as such.
❌ Actual Behavior
All recipe.yaml or recipe.yml files are validated with the rattler-build schema, causing meaningless validation errors for all YAML files that are named in this way but aren't rattler-build files – likely a large majority of such files.
I have no clue what more specific naming rule would be suitable for rattler-build, but it seems wrong to assume that all YAML files with basename recipe are rattler-build files.
As a workaround I created my own Schema store here, and configured that URL e.g. for VS Code in the Yaml > Schema Store > Url setting.
YAML or JSON file that does not work.
No response
IDE or code editor.
Any/All
Are you making a PR for this?
Happy to open a PR for this or whatever else works, but actual rattler users should probably decide what specific naming convention to use.
The text was updated successfully, but these errors were encountered:
Area with issue?
JSON Schema (actually YAML)
✔️ Expected Behavior
Only actual rattler-build YAML files get validated as such.
❌ Actual Behavior
All
recipe.yaml
orrecipe.yml
files are validated with the rattler-build schema, causing meaningless validation errors for all YAML files that are named in this way but aren't rattler-build files – likely a large majority of such files.I have no clue what more specific naming rule would be suitable for rattler-build, but it seems wrong to assume that all YAML files with basename
recipe
are rattler-build files.As a workaround I created my own Schema store here, and configured that URL e.g. for VS Code in the
Yaml > Schema Store > Url
setting.YAML or JSON file that does not work.
No response
IDE or code editor.
Any/All
Are you making a PR for this?
Happy to open a PR for this or whatever else works, but actual rattler users should probably decide what specific naming convention to use.
The text was updated successfully, but these errors were encountered: