Vscode: Monolithic structure, multiple project settings

[thetrompf]

I was wondering if it is possible for VSCode to pick up on multiple .vscode/settings.json

For instance if you are working in an monolithic environment with multiple smaller projects inside it, and each have their own .vscode/settings.json.
Can VSCode pickup on that, and apply the settings from the smaller projects .vscode/settings.json to their subtree and descendant files?

monolithic-project/
├── small-project1/
│   ├── .vsocde
│   │   └── settings.json
│   └── src/
│       └── index.ts
└── small-project2/
    ├── .vsocde
    │   └── settings.json
    └── src/
        └── index.ts              

Wanted effect:
monolithic-project/small-project1/.vscode/settings.json applies to monolithic-project/small-project1 and all descendant files.
monolithic-project/small-project2/.vscode/settings.json applies to monolithic-project/small-project2 and all descendant files.

[sandy081]

Supporting folder settings at any level is a good idea and is similar to editor config.

FYI Currently we are working on a multi root workspace where you can have multiple root folders. In this case settings under each root folder are applied to the resources under the respective folder (just as you mentioned). But all such folders should be root folders (small-project1, small-project2). This feature is available only in insiders. See #28344 for more details.

Please close this request, if multi root workspaces full fill your requirements

[thetrompf]

Thank for the reply, I am aware of the progress in this area, but if you
have a monolithic repo with multiple small projects inside that lives on
the different levels on the filesystem and you add the root of the repo as
a root in a multi root workspace, and then you add folders from within the
project root to appear at top level, it will possibly break the experience
of quick open, where the same file would appear multiple times, the same
goes for search, or I would have to manually exclude the folders that has
been added as a workspace roots from the project root's file system.

I think the experience would be a lot nicer if VSCode could handle
multiple. vscode roots and make them apply to their respective sub trees.

It would really shine if it could pick up on launch.json as well so I could
choose the list of available launch profiles based on the active file in
the editor.

On Mon, Aug 21, 2017, 4:45 PM Sandeep Somavarapu [e-mail]
wrote:

Supporting folder settings at any level is a good idea and is similar to
editor config.

FYI Currently we are working on a multi root workspace where you can have
multiple root folders. In this case settings under each root folder are
applied to the resources under the respective folder (just as you
mentioned). But all such folders should be root folders (small-project1,
small-project2). This feature is available only in insiders. See #28344
https://github.com/Microsoft/vscode/issues/28344 for more details.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/32693#issuecomment-323761494,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABXSZo-X_5X-4cbuz5TDVua3vLeUnfREks5saZf_gaJpZM4O50vl
.

>

Med venlig hilsen / Best regards
Brian K. Christensen

[DanTup]

I raised a case that I think covers this (but also a bit more) at https://github.com/Microsoft/vscode/issues/45399. This extends to more than just settings, but also launch configs/etc.

[thetrompf]

You're right it just extends to multiple .vscode directories. Settings, launch, tasks and etc.

[shridharkalagi]

I have landed in a similar situation. Is this resolved in the latest version?

[thetrompf]

Unfortunately is still experience exactly the same as stated in the issue
description.

Med venlig hilsen / Best regards
Brian Kejlberg

man. 21. jan. 2019 12.07 skrev Shridhar Kalagi [e-mail]:

I have landed in a similar situation. Is this resolved in the latest
version?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/32693#issuecomment-456035663,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABXSZkEZtHKYnFb_u4V2HUk-cFnRWYYvks5vFZ9ggaJpZM4O50vl
.

[shridharkalagi]

Is this in the backlog of issues to be fixed? Any workaround till then?

[xujintao]

@DanTup
after https://github.com/microsoft/vscode/issues/45399 then https://github.com/microsoft/vscode/issues/45470
So, do vscode support mono or not? if not, which issue should be followed?

[DanTup]

@xujintao it depends a lot on your project structure and language. For Dart/Flutter, it's a little wonky without https://github.com/microsoft/vscode/issues/45470, but we have made some improvements to find our own project roots instead of using multi-root workspaces.

[memark]

Any update on this? Still would be a really helpful feature!