How to set Schema to No JSON Schema

[bitstarr]

When I open a site config for grav cms (like this) VS Code will use 'Ansible Playbook' as schema, but I don't want to use any schema on that file.

Who do I disable this behaviuor? I'm so annoyed by this.

[gorkem]

This is because schema store catalog maps site.yaml to Ansible Playbook. One way to fix this is to set yaml.schemaStore.enable and disable automatic schema store matching. Alternately you can set the mapping for site.yaml explicitly on settings to override the schema store.

[filcuk]

Just for anyone else looking for how to set the custom mapping, add the following to VSC settings.json:

"yaml.schemas": {
  "none": "site.yaml"
}

[davetapley]

See also:

• Ability to specify schema as a comment in the YAML file #401 (comment)

[AndiDog]

Can we add a menu entry to choose "No schema"? Otherwise the whole editor is full of red underlines, making the file unreadable. I don't want to turn some global setting off since the feature is generally helpful. But if the auto-matching fails, I want to set "No schema" once.

[thardy]

That would be far too intelligent. The ability to actually set the schema to "None" after clicking "Select JSON schema" in the IDE?

You sir, are talking crazy. It makes much more sense to force people to google changing a global setting or pollute their file with some functional comment than allow people to set the schema to "None"/"No Schema"/"No JSON schema" where they can choose the schema. We have UX professionals for this, and they say you are wrong. Users prefer to be mystified and have to google how to accomplish something rather than being able to figure out how to do something just by looking at it.

Away with you and your crazy ideas.

[lexicalunit]

I ran into this bug today because a file was named rules.yml which was auto-mis-detected as Prometheus configuration file. Certainly useful for that auto detection to exist. But it is also exceedingly strange that you can't choose "No JSON Schema" as an option in the Select JSON Schema menu and instead have to hack in a workaround. Seems like it would be an easy fix.