Allow disabling project addons
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2k
- Forks
- 281
- Avg merge
- 2h 14m
- Merged PRs (30d)
- 6
Description
I have checked that this feature is not already implemented
- This feature does not exist
Use case
I want to execute Ruby-LSP as vanilla as possible (i.e. only to provide code navigation), without any interference of gems in the project, such as Standard/Rubocop/etc.
Description
I see that this is partially implemented on Server class, but it's currently not exposed through any interface.
Are there any plans to allow users to permit/block project addons?
Implementation
I would keep it under an initialization flag.
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
Read lib/ruby_lsp/server.rb around lines 176 and 357, then trace how server initialization options are exposed to users. Define the configuration path for permitting or blocking project addons, and verify that vanilla operation can disable them without affecting code navigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100