Gorkem Ercan

seems like a duplicate of https://github.com/redhat-developer/yaml-language-server/issues/875

@remcohaszing I think we will have to move to a later vscode-json-languageservice not only to get schema support for more recent schema versions but also for issues like #823 are...

No problem. Unfortunately, there are breaking changes on vscode-language-service that we need to adjust yaml-language-server for.

This should be setting to exclude them. Otherwise, LSPs do have a way to mark deprecated code completions as deprecated and we should actually use that mechanism instead of excluding...

Deprecated APIs are common in programming languages. Typically language tooling deals with it, not by removing them without notice but by marking them. Deprecated properties can be marked as deprecated...

A complete solution would be to enable the deprecated hint (the cross out) and add a setting (not a schema property) to not suggest the deprecated properties. I do not...

We do inherit the `doNotSuggest` property from vscode json language service. As far as I can see on the JSON land it only applies to properties. Although I think this...

We are using vscode-json-langaugeservice to resolve schemas. This has been fixed upstream, we probably need to adjust to this later version.

The referenced support is specific to the Typescript language server. We do not have equivalent functionality but support an [extension API ](https://github.com/redhat-developer/vscode-yaml/wiki/Extension-API) that allows plugins to update the schema used...

It is not really on our plans but that does not mean we would not accept it. However, before doing a PR can you write an RFC about what kind...