puppetlabs / puppetlabs/puppet-editor-services
Puppet Editor Services don't attach to puppet files
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 52
- Forks
- 21
- Avg merge
- 15h
- Merged PRs (30d)
- 3
Description
Describe the Bug
I installed the puppet editor services via mason in neovim 0.11.4 on ubuntu 24.04.
When I open a puppet manifest file I don't get any code actions, code navigation or anything. LSPLogs are clear. No errros.
Expected Behavior
After installing the editor services the lsp should provide its functionality in neovim.
Steps to Reproduce
Steps to reproduce the behavior:
MasonInstall puppet-editor-services- open puppet file
Environment
- Version 2.0.4
- Platform Ubuntu 24.04
- Ruby 3.4.7
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 issue with MasonInstall puppet-editor-services in Neovim 0.11.4, then open a Puppet manifest on Ubuntu 24.04 and inspect the editor-service attachment and LSP behavior. Done means the Puppet language server attaches to the file and provides code actions and code navigation without errors in the LSP logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100