Inconsistent validation based on file extension (file.yml vs file.yaml)

Upon saving a yaml file as .yml previous valid yaml syntax reports invalid.

Operating System: Windows 10 VS Code Release: 1.43.1 YAML Extension Version: 0.7.2

Steps to reproduce:

1. Open a new workspace.
2. Set language mode to YAML.
3. Insert valid yaml syntax, for example:

plugins:
  - name: "Plugin 1"
    date: "Mar 21 2020"
    licenseKey: |
      line1
      line2

  - name: "Plugin 2"
    date: "Mar 21 2020"
    licenseKey: |
      line1
      line2

1. Save file without specifying extension (defaults to .yml)

File > Save > “fileName”

At this point all previously valid syntax reports ‘Incorrect type. Expected “string”.’

1. Save file specifying the yaml extension.

File > Save as > “fileName.yaml”

All syntax now reports correct again.

Specifically the filename I tested with is “myAppConfig” and follows the exact same formatting as above. It is being saved in the default Windows 10 document folder and using “Spaces 2” indentation. Verified no trailing white space and that both files validate fine with a up to data Python3 yamllint install.

[vdh]

@JPinkney Which schema file…? This is the issue.

Other linters like ESLint or Typescript will identify themselves in the Problems pane, and directly link to their validation source (ESLint with external doc links, or TS with error codes). vscode-yaml is anonymous and lacking any info to trace which schema is complaining, thereby making it impossible to find false-positives and fix them.

[gorkem]

Extending diagnostics is a good idea opened https://github.com/redhat-developer/yaml-language-server/issues/310