yaml.schema incorrectly flags property

My coc-settings.json file has the following setting:

{
  "yaml.schemas": {}
}

That’s not a typo. I do not have any yaml schemas configured in my coc-settings.json file.

The Problem

When I edit a yaml file in .semaphore/deploy.yml, coc-yaml flags all the top-level properties as invalid with the following message:

[yaml-schema: https://raw.githubusercontent.com/deployphp/deployer/master/src/schema.json] [E] Property version is not allowed.

Why is coc-yaml pulling a schema from deployphp/deployer? This doesn’t happen for all yaml files.

[egyptianbman]

This seems to be an issue with how https://www.schemastore.org/api/json/catalog.json is parsed. GitHub Workflow has .github/workflows/**.yml defined but if your file ends in deploy.yml, it’s caught first by Deployer Recipe

[daogilvie]

Appreciate this issue has been open for a while, found it whilst googling as I have the same problem.

I have a GCP cloudbuild.yaml file that I just could not get the LSP to point the right schema at, because it ended in build.yaml it kept pointing the hammerkit schema at it. ¯_(ツ)_/¯

I am just adding that the latest release of the language server has nothing about this in their changelog so I suspect it’s not been fixed. In any case, I have found a workaround that suits me:

I disable the schema store in my global config: "yaml.schemaStore.enable": false Then do the mapping as normal in local:

  "yaml.schemas": {
    "http://json.schemastore.org/cloudbuild": ["cloudbuild.yaml"]
  }

Hope this helps anyone else who might still have the issue.