yaml-language-server VS js-yaml

Does anyone know how to get yaml formatting working with yamlls (https://github.com/redhat-developer/yaml-language-server)?

I'm starting to work with kubernetes and it would be really nice to have the full completion that Redhat's language server offers for k8s yaml files if you associate the right schema with it.

Most modern editors and IDEs support the Language Server Protocol, which powers the code completion, validation, and tooltip features. Combined with a Yaml Language Server, we can get rich completion for Yaml files!

I don't think the YAML language server can handle this. Here's the issue about this: https://github.com/redhat-developer/yaml-language-server/issues/220

Here's an example .dir-locals.el configuration I'm using with yaml-language-server

Check out https://github.com/redhat-developer/yaml-language-server if you want to get that IDE experience with YAML from those openapi specs

For our custom LSP, we'll start by forking the yaml-language-server maintained by redhat.

One of the things I was missing in my nvim setup was the ability to choose the schema that yamlls uses in the various buffers. This server also intentionally leaves out some cool features like content aware schema detection and, since I could never get the Schema Store functionality to work when paired with the hard-coded Kubernetes support in the language server… I have converted all the hacky lua I had into this plugin. Sharing it here in case it is useful to anyone https://github.com/someone-stole-my-name/yaml-companion.nvim

Parse the source string. We're using js-yaml for this.

Character limit is not enforced, and in practice, popular yaml implementations such as yaml/js-yaml don't impose any fixed limit.

The main reason behind this release is native YAML support in front-matter thanks to js-yaml library. This means you have to assign the tags key as yaml arrays otherwise, Action will throw an error or ignore the assigned tags.

js-yaml