Open gookyn opened 2 years ago
As of today, we can't do this. It's set to one workspace because of the choose workspace feature we have.
Once we get rid of that, then I can start to look at the vscode workspace apis and make things work that way.
With a vscode workspace you can have multiple projects opened and extensions should be able to handle those situations, but again, right now NX Console can't do that.
Currently, NX console is interfering with some other VS Code plugins when multiple NX workspaces are used inside a single vscode workspace.
For example, Orta's Jest runner can only find tests in the currently selected NX workspace.
Also, any command running any "nx" based target (for example, git commit hook using husky to run lint-staged then configured to run nx affected:lint and nx:format:write .. just because things are easier this way ... ) will always run in the currently selected workspace.
This means you are committing a change on project A, but the commit fails because of a lint problem on project B.
I haven't investigated the code, but I suppose both these problems are connected to a sort of env variable or similar thing that redirects any "nx" call to a specific folder.
That clearly explains the git problem, but also the Jest problem, given that also the jest configuration gets redirected to some NX internals, which gets redirected to NX console, which redirects it to the only supported folder.
If you are developing multiple NX projects in the same workspace, I would advise you disable the NX console plugin, and re-enable it when really really needed.
Description
When I have multiple Nx projects in my workspace, I can only select one of them for display.
Is it possible to support more than one?
Motivation
I often develop multiple projects in one workspace, it will be more convenient to work if it can support multiple Nx project display.
thx!
Suggested Implementation
Alternate Implementations