Allow disabling project addons

[kriansa]

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.

[egiurleo]

Hi, @kriansa! We don't have any capacity to work on this right now, but if you wanted to open a PR, we'd b happy to review.

[vinistock]

Hey, @kriansa. Can you explain why you'd want to disable an add-on? In your specific example, would turning off auto formatting be enough?

[domingo2000]

I found this to be usefull in our organization. We created an addon that some users like, but other don't, for example because of code lens they do not use and make noise in their editor.

Also some addons can consume some CPU/Ram resources in low end PCs.

We had to implement the enable/disable logic in the addon itself. But it should be nice if this is standarized for all addons based on the addon settings. I opened a PR to address this issue, happy to get feedback.