yaml-language-server VS www.yaml.org

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

First of all, create a file in the root project directories called compose.yaml. YAML is a text format that uses indentation to specify dependencies between configuration options. Be aware that incorrect indentation will cause problems with executing commands properly.

Most commonly written in YAML, these files are large and complex to read and understand. And being written in YAML comes with its challenges (and quirks) since it is an additional programming language that devs need to learn.

YAML Ain't a Markup Language

Note, that this file is a Markdown and YAML file at the same time, and as such human- and machine-readable, if the fields are filled carefully.

Front matter is a bit of text at the start of a file (YAML to be exact) that is placed between two ---

Meanwhile, formats have been evolving (JSON5, YAML), config entry points are constantly changing. These fluctuations, fortunately, were covered by tools like the cosmiconfig.

Personally, I'd love to see them using a standard file format like TOML or YAML so that they're easy to parse and work with using already-existing tools.