Provide a way to enable linters/formatters by directory without deactivating the extension

[noirbizarre]

Hi 👋🏼

Extracting linters and formatters into their own extensions was a good move in my opinion, but we lost some important features because before it was possible to:

• to toggle them by directory in multiple root workspace, not possible anymore if the only way is to disable the extension
• to mix them in a multiroot workspace (eg. have flake8 as project-a linter and pylint as project-b linter), not possible anymore, they are either active on the entire workspace or totally disabled (so you need to chose only one, deactivate the other or else you only have false positive)
• to toggle them without VSCode restart (deactivating a linter extension requires a restart)
• to toggle them from configuration file (which are versionnable and shareable), not possible anymore, extensions are exclusively managed by VSCode internals

So, given they use a common base template, is it possible to restore those behaviors by:

• adding <extension namespace>.enabled boolean setting
• ensure it is working by directory and not by workspace (this is very important for multiroots workspaces)
• bonus: make this setting apply without a restart

[karthiknadig]

@noirbizarre we have a ".ignorePatterns" that can be used temporarily as a workaround to skip any directory or workspaces. You can use ${workspaceFolder:<name>} as a shortcut to skip a particular workspace.

We do plan on adding a boolean setting to the extensions.

[noirbizarre]

Thanks for the quick response!
That's very good news! 🎉

Is there an issue I can track on the topic or is this still an internal backlog/roadmap currently?

Thanks for the workaround, I'll try it until this is implemented 🙏