yaml.schemas priority is lower than schemaStore

I was trying to use vscode-yaml for ansible configuration recently, specifically this one schema http://json.schemastore.org/ansible-stable-2.9 but there’s a small bug where yum supports only string as input.

Afterwards I’ve added configuration to use custom schema

"settings": {
		"yaml.schemas": {
			"./ansible-stable-2.9-local.json": "*",
		}
	}

I guess that file loads properly, because on hover it gets proper description for properties and autocomplete, but validation not.

After I’ve added "yaml.schemaStore.enable": false, to settings I am getting both hover information and rules from local file.

[alex-kinokon]

Still reproducible.

[JPinkney]

filePatternsAssociations stuff is all passed through to the JSON language service IIRC.

I think to fix this issue we need to introduce priorities for schemas like suggested. Something like https://github.com/redhat-developer/vscode-yaml/issues/151 should always be priority 1, meaning that if it is present, no matter what it will use it and nothing else.

Then I think local schemas can be priority 2, meaning any other local schemas can be matched with the file.

Then schema store schemas would be priority 3 and are only used if nothing else matches.