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
Is your enhancement related to a problem? Please describe.
Because of a bug in SchemaStore, my YAML files named *.es.yaml get incorrectly recognized as fulibWorkflows making the IDE suggestions useless.
Describe the solution you would like
I'm stuck with these names on the files, so I'd want to just disable the JSON schema check.
Describe alternatives you have considered
I think having a null/noop/None option to unset the schema would be useful. Alternatively, we could have a checkbox in the settings to disable the schema validation, but I prefer a null schema because it's easier to change on a file-by-file basis then.
I know of no good alternatives to this. While I would like to see the bug in SchemaStore get fixed, the feature I suggest here would be useful more generally (not just as work-around for that particular bug).
I guess one alternative could be to disable the YAML integration in VSCode, but that's far from ideal… 😕
Additional context
This has already been discussed in #939 but it seems to have been abandoned, so I'm opening this instead.
The text was updated successfully, but these errors were encountered:
Is your enhancement related to a problem? Please describe.
Because of a bug in SchemaStore, my YAML files named
*.es.yaml
get incorrectly recognized asfulibWorkflows
making the IDE suggestions useless.Describe the solution you would like
I'm stuck with these names on the files, so I'd want to just disable the JSON schema check.
Describe alternatives you have considered
I think having a null/noop/None option to unset the schema would be useful. Alternatively, we could have a checkbox in the settings to disable the schema validation, but I prefer a null schema because it's easier to change on a file-by-file basis then.
I know of no good alternatives to this. While I would like to see the bug in SchemaStore get fixed, the feature I suggest here would be useful more generally (not just as work-around for that particular bug).
I guess one alternative could be to disable the YAML integration in VSCode, but that's far from ideal… 😕
Additional context
This has already been discussed in #939 but it seems to have been abandoned, so I'm opening this instead.
The text was updated successfully, but these errors were encountered: