IssueRaiser

Monolithic structure, multiple project settings

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.

Posted by thetrompf on Aug 17, 2017, 6:19 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments

github (Logistics)

Monolithic structure, multiple project settings

thetrompfAug 17, 2017, 6:19 AM

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.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue