YAML

1# Bundled YAML server: `yaml-language-server`, the one behind Red Hat's VS Code2# YAML extension. Installed by `pnpm lsp:install`. See LSP-SERVERS.md.3#4# This server brings its own SchemaStore support, so unlike the JSON one it5# needs no catalog from Tori - only for `[settings]` below to reach it. Which is6# less obvious than it sounds: it answers `workspace/didChangeConfiguration` by7# *pulling* its configuration back with `workspace/configuration`, and it is8# that answer, not the push, that carries these values.910schema_version = 111id = "yaml"12label = "YAML"13description = "YAML with SchemaStore schemas, through yaml-language-server"14license = "Apache-2.0"15contributor = { name = "Tori", github = "gettori" }1617# `.git` alone, for `json.toml`'s reason: nothing about this server is18# per-package, so a marker that appears in every package of a monorepo would19# buy a session per package and no correctness.20root_markers = [".git"]2122verified_against = "yaml-language-server 1.24.0"23verified_on = "2026-08-05"2425# Reads documents and fetches schemas but executes nothing from the project, so26# it keeps working in a project the user has not trusted.27runs_project_code = false2829[languages]30yaml = "yaml"31yml = "yaml"3233[launch]34kind = "bundled_node"35entry = "resources/lsp/node_modules/yaml-language-server/bin/yaml-language-server"36args = ["--stdio"]3738# The server's own defaults are these values, but a default it never reads is39# not a default it applies: its schema store is only built inside the40# configuration handler, which does not run until a configuration arrives. So41# this table is what turns SchemaStore on, restating the defaults rather than42# changing them.43[settings.yaml]44validate = true45completion = true46hover = true4748[settings.yaml.schemaStore]49enable = true50url = "https://www.schemastore.org/api/json/catalog.json"