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
If you have a schema comment, VSCode-YAML will try to use the schema mentioned and the schema(s) it finds in schema store, creating nonsensical problems.
Expected Behavior
The schema in the comment should override the schema the YAML extension/language server gets from the schema store.
Current Behavior
Both schemas are being used simultaneously, with the one from the schema store being prioritized.
Steps to Reproduce
Load a file that vscode-yaml thinks has a match in the schema store, even if it really doesn't match.
Make sure that file has a schema comment somewhere in the file. (#yaml-language-server $schema=...)
Note that the schema that vscode-yaml finds isn't being overridden by the schema comment, like it was pre 1.0.
Environment
Windows
Mac
Linux
other (please specify)
Sample file attached. If this is intended behavior for some reason, we'll need to remove our paths from the schema store since they aren't working. I can't imagine why it would be intentional though.
Describe the bug
If you have a schema comment, VSCode-YAML will try to use the schema mentioned and the schema(s) it finds in schema store, creating nonsensical problems.
Expected Behavior
The schema in the comment should override the schema the YAML extension/language server gets from the schema store.
Current Behavior
Both schemas are being used simultaneously, with the one from the schema store being prioritized.
Steps to Reproduce
#yaml-language-server $schema=...
)Environment
Sample file attached. If this is intended behavior for some reason, we'll need to remove our paths from the schema store since they aren't working. I can't imagine why it would be intentional though.
Thanks!
Obsidian.Obsidian.installer.yaml.txt
The text was updated successfully, but these errors were encountered: