Feature Request: Enable/disable extensions from config file

[roaldarbol]

First of all, I only learned about Theia the other day, and am very excited about the project! Have been using VSCodium for years, but am likely making a full switch here - great work!

Feature Description:

It seems that, currently like VSCode, it's not possible to enable extensions per project. That would be immensely useful, and it has been one of the highest ranked issues over there for years. I feel like Theia would be a better candidate to actually resolve that issue!

Rather than coming with a suggestion, I'll point to the discussion on the VSC feature request:

• Feature Request: Enable/disable extensions from config file microsoft/vscode#40239

A useful summary/discussion of a few possible solutions is here: microsoft/vscode#40239 (comment)

This feature request would also cover related Theia issues (might be more, just came across this):

• Make built-in extensions deactivatable ( disable ) #13876

[rschnekenbu]

@roaldarbol, huge thanks for your support and for using our tool! We greatly appreciate your engagement and these kind messages.
Your suggestion for this extension management looks good, and I can understand how it could be beneficial to many users.
Additionally, there are other similar issues that we're collecting requirements for, such as #13282 and #7558. Gathering these requirements is a great first step towards developing a comprehensive solution.

As you may already know, Theia does not support the core feature of enabling / disabling the extensions. They can be (un)installed, but no enablement is currently implemented. This would be the first step towards the kind of feature you suggest.
Would you be interested in contributing to such feature? It seems you have been thinking for quite some time on this