Allow to disable schema validation for certain file patterns

[hadim]

Some YAML files are valid but cannot be validated using a regular YAML schema because they contain jinja content, for example.

It makes it quite annoying to work with YAML file with VSCode and no real alternatives YAML plugin and LS exist so far.

For background, I have collected a few related GH issues:

• How to disable validation for conda meta.yaml? #665
• Disable schema detection for certain files #245
• Ansible incorrect type errors when using Jinja #298
• Support for .tpf (Helm chart Yaml-based template files) yaml-language-server#220
• Cannot set up redhat.vscode-yaml as formatter for ansible. #812

---

I can see two options to fix that:

• Option 1: "somehow" allows the YAML validator to either validate or ignore jinja content.
• Option 2: allow a user to disable YAML validation in VSCode for specific files or file patterns.

[terekete]

Is there any option on the plugin to stop highlighting of jinja as an error ?

[debuggerpk]

this would be highly desirable.

[psych0d0g]

option 2 would be nice for us, this would allow one who uses kustomize overlays without the yaml validator complaining about incomplete schemas (this is by design if one just patches certain areas of a base yaml file within the overlay)

[unional]

Workaround:
#245 (comment)

You can create empty-schema.json locally. e.g.:

// .vscode/yaml/empty-schema.json
{}
```

[geekley]

This is also important to stop errors in Unity's asset files, like *.asset, *.scene, etc.
The workaround of using an empty schema like https://www.schemastore.org/any.json doesn't work, because the issue is with unity's tags being flagged as errors. Currently, I can only disable validation globally, or add a gigantic list of tags to my settings, which is absurd (see #1156).

I should be able to disable validation per file pattern, this is a very essential feature as YAML could be used by all sorts of purposes, with all sorts of potential false-positive errors without a proper schema and custom tag settings.
If I disable the file association for a custom YAML format, I don't get syntax-coloring either.