Enable configuration per folder

[kallookoo]

Hi,

Could you allow to configure the extension per folder? Now you can by workspace but sometimes the project configuration is inside the .vscode folder and you can't configure it or you have to configure it manually in the workspace so it's not practical when you share the configuration with other people or you download it from a Github repository.

[CaffeineOnIce]

I'll just make a big update by the end of this month, but trust me, vscode api is so dogshittily documented, I have to take help of deepseek or qwen for editing this pile of shit. But apart from that, configuration per folder will be a bit complicated and I don't really understand what you mean. Could you please elaborate a bit further?

[alainbastard]

Hi,

Just to elaborate what I think kallookoo means, is that we would like to have multiple settings.json to be able to change the settings per project: if we open a workspace at a location (let's use /projects for example), it would be nice to have different settings.json parsed at /projects/firstProject, /projects/secondProject, etc.
This would help a lot, as the projects are NOT always structured identicals...
I hope my text clarifies this demand !

[CaffeineOnIce]

Hi,

Just to elaborate what I think kallookoo means, is that we would like to have multiple settings.json to be able to change the settings per project: if we open a workspace at a location (let's use /projects for example), it would be nice to have different settings.json parsed at /projects/firstProject, /projects/secondProject, etc. This would help a lot, as the projects are NOT always structured identicals... I hope my text clarifies this demand !

ahhh, got it. per workspace or per folder settings you mean? hmm that'll require some work. I'm planning to push out an update by this month, let's see what I can achieve.

[alainbastard]

Hi,
I just found out that feature as mentioned by kallookoo:
https://code.visualstudio.com/docs/editor/workspaces/multi-root-workspaces
So, using the multi root workspaces is already an option, but it seems to be painful to do so...
I don't know if the time needed for development is massive or not... You tell us !

[kallookoo]

The visual code, can obtain the options of the user (global), workspace and from the folder .vscode that is inside the folder where you are working.
Therefore and from what I know, the problem is that it is not updated according to the context. But it is only a deduction. First let's wait for the new version and see how it behaves.

REF: https://code.visualstudio.com/api/references/vscode-api#WorkspaceConfiguration

[kallookoo]

Hi,
I am currently making (testing) my own extension and I have seen that the problem is in the lack of the "scope" defined as resource. See https://code.visualstudio.com/api/references/contribution-points#contributes.configuration (section "scope") so the vscode only shows the extension options by default in User and Workspace.

Summarizing: Until you do not specify the scope in resource for the settings, you will never be able to customize the extension options per folder.