You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello. The extension is great, except one thing, which renders the extension unusable to me:
It alters [workspace].code-workspacewhen 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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: