Skip to content
This repository was archived by the owner on May 2, 2022. It is now read-only.
This repository was archived by the owner on May 2, 2022. It is now read-only.

Consider depending on VSCode-YAML rather than directly on yaml-language-server #130

@JPinkney

Description

@JPinkney

Hi,

from looking into your repository it looks like you use the yaml language server directly rather than relying on VSCode-YAML for the YAML support. I was wondering if there is any particular reason why you spawn up the language server yourself, rather than just using VSCode-YAML as an extension dependency and having that spawn it. If you are doing this because there are some API's missing that you need then please let me know.

The only reason I bring this up is this has been done before and it will eventually lead into multiple language servers running for a yaml file if the user has vscode-yaml and this extension installed. This can create several unintended results like duplicate completions, etc etc.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions