redhat-developer / redhat-developer/yaml-language-server
yamlls + schema working fine in neovim?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 352
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 11
Description
Summary
I've setup yamlls + neovim & neovim-lspconfig + a bunch of other LSPs and so far it was all working fine..
Now for yamlls I've also set the schema github-workflow.json from schemastore and it seems to work .. at least for the most part.
While adding "on" events I get completion suggestions just fine but "runs-on" for the runner I don't see anything.
Let me provide some details in this quick vid:
Relevant information
Checking log file lsp.log trying to debug I didn't get much details.. this is basically all I found in the logs:
[START][2024-04-02 03:59:22] LSP logging initiated
[WARN][2024-04-02 03:59:22] ...lsp/handlers.lua:134 "The language server yamlls triggers a registerCapability handler for workspace/didChangeWorkspaceFolders despite dynamicRegistration set to false. Report upstream, this warning is harmless"
[WARN][2024-04-02 03:59:22] ...lsp/handlers.lua:134 "The language server yamlls triggers a registerCapability handler for workspace/didChangeConfiguration despite dynamicRegistration set to false. Report upstream, this warning is harmless"
For yamlls I don't have customizations, the only thing I've added to the default settings was the schema from schema store..
checkhealth apparently is fine as well, Treesitter seems fine showing yaml parser installed, vim.lsp active clients show yamlls attached just fine..
Any suggestion?
Is this completion working fine in neovim btw?
System: Mac M1 14.4.1
NVIM v0.10.0-dev-a84b454
yaml-language-server 1.14.0
mason 751b1fc
Thanks in advance
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the missing runs-on completion in Neovim with yamlls 1.14.0 and the github-workflow.json SchemaStore schema, then inspect the reported LSP behavior and logs. Done means completion suggestions appear for runs-on as they do for on events, with the result verified in Neovim.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- neovim, typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100