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

selecting workspace folders alters the workspace configuration #93

Open
akomm opened this issue May 12, 2021 · 1 comment
Open

selecting workspace folders alters the workspace configuration #93

akomm opened this issue May 12, 2021 · 1 comment

Comments

@akomm
Copy link

akomm commented May 12, 2021

Hello. The extension is great, except one thing, which renders the extension unusable to me:

It alters [workspace].code-workspace when switching workspace folders (its okay when it syncs packages). You understand that the purpose of this file is storing project (monorepo) settings to other vs-code users? If it keeps changing for every user individually workspace selection, you have to .gitignore it, which renders the purpose of storing cross-user settings pointless - extension recommendations btw. indicating the point of file is to share, not to ignore - why should I recommend extensions to myself?

Is there any way to prevent or workaround this behavior? TI hope there is a solution because otherwise the extension is great. Thanks in advance.

@capybarahero
Copy link

Hey there,

I am afraid I am stumbling on the issue you described above. In short:

We'd like to have custom workspaces - i.e. with predefined selected of folders and terminals - and would like to have these .code-workspace files saved on the repo.

The problem is the Monorepo extension just overwrittes these files once we switch from these custom workspaces to the Monorepo extension-created workspaces.

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

No branches or pull requests

2 participants