Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] - Multiple folders for a project #777

Closed
jandroav opened this issue Dec 7, 2024 · 2 comments
Closed

[FEATURE] - Multiple folders for a project #777

jandroav opened this issue Dec 7, 2024 · 2 comments

Comments

@jandroav
Copy link

jandroav commented Dec 7, 2024

I have a Terraform project made of several modules in a monorepo. I would like to create a project with the needed folders to easily work on it instead of folding and unfolding stuff. I thought the paths should do the trick:

[
	{
		"name": "myproject",
		"rootPath": "/Users/jandroav/workspace/infrastructure/aws-control-tower/root-ou/engineering-io-ou",
		"paths": ["/Users/jandroav/workspace/infrastructure/modules/shared", "/Users/jandroav/workspace/infrastructure/modules/tenant"],
		"tags": [],
		"enabled": true
	}
]

Is it possible?

@alefragnani
Copy link
Owner

Hi @jandroav ,

I think the native Multi-root workspace would work great for your scenario. You could even save the .code-workspace file (which stores the multi-root configuration) inside the monorepo.

That paths attribute was created a bit before the multi-root workspace feature landed on VS Code, with the same purpose. But, once multi-root appeared, it became outdated and in fact, will be removed.

In the extension's side, the #677 would be an alternative. You define a new tag, apply it to each desired repo, and open all of them at once.

Hope this helps.

@alefragnani alefragnani closed this as not planned Won't fix, can't repro, duplicate, stale Dec 7, 2024
@jandroav
Copy link
Author

jandroav commented Dec 9, 2024

Hi @jandroav ,

I think the native Multi-root workspace would work great for your scenario. You could even save the .code-workspace file (which stores the multi-root configuration) inside the monorepo.

That paths attribute was created a bit before the multi-root workspace feature landed on VS Code, with the same purpose. But, once multi-root appeared, it became outdated and in fact, will be removed.

In the extension's side, the #677 would be an alternative. You define a new tag, apply it to each desired repo, and open all of them at once.

Hope this helps.

Thanks a lot. Really helpful!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants