redhat-developer / redhat-developer/yaml-language-server

How to configure yamlls at a workspace level for neovim?

Open
#961 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
1.5k
Forks
352
Avg merge
2d 7h
Merged PRs (30d)
11

Description

Summary

I mainly work with 2 types of YAML files. (In two separate projects)

  1. Cloudformation Templates
  2. OpenAPI 3.0.0 specs

And the inbuilt validator doesn't work too well with these. So I wanted to disable yamlls' validator for these two projects.

But the best I was able to do was disable it in my nvim-config, far from an ideal solution.

    lspconfig.yamlls.setup({
        settings = {
            yaml = {
                validate = false,
            }
        }
    })

I also tried configuring .vim/settings.json but that had no effect.
Please let me know how to configure this (or any other) LSP at a workspace level.

P.S: If it's possible to also specifically provide cloudformation schema or OpenAPI schemas for particular files/folders, that would be great!
But I digress.

Relevant information

yaml-language-server:

installed version 1.14.0
Path: /Users/<username>/.local/share/nvim/mason/bin/yaml-language-server --stdio

neovim:

NVIM v0.10.0-dev-2961+g4d52b0cf6
Build type: RelWithDebInfo
LuaJIT 2.1.1713484068

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by examining the lspconfig.yamlls.setup example and the attempted .vim/settings.json configuration described in the issue. Determine whether workspace-level validation settings and per-file or folder schemas are supported, then document or implement a clear configuration path and verify it in separate CloudFormation and OpenAPI projects.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua, typescript, yaml
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.