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
At the moment, the extension detects my backend tests twice, once as a subdirectory of the root project and once as a subdirectory of the "service" project which is a bit confusing and unnecessary.
I would like to be able to configure this extension on a per-subproject level and use it only for the backend subproject and disable it for the UI one and for the root project (which has no code of its own). Is there a good way to do that now? VS Code only seems to allow me to configure it in the root project.
The text was updated successfully, but these errors were encountered:
in my root workspace's config, because the only project where that's a valid path is the one I want it to scan, but I can see that it's actually applying that setting to each workspace in my project individually because if I create tests under that path in one of the other workspace directories, they show up too in VS Code.
I have a monorepo setup which uses a VS Code Multi-root Workspace. In this project I have two subprojects, one for a backend NodeJS service and one for a React UI. I use node's test runner for the backend project but for the UI tests I use other tools. My project setup in case it helps: https://github.com/pfaffle/armada-analyzer/blob/main/armada-analyzer.code-workspace
At the moment, the extension detects my backend tests twice, once as a subdirectory of the root project and once as a subdirectory of the "service" project which is a bit confusing and unnecessary.

I would like to be able to configure this extension on a per-subproject level and use it only for the backend subproject and disable it for the UI one and for the root project (which has no code of its own). Is there a good way to do that now? VS Code only seems to allow me to configure it in the root project.
The text was updated successfully, but these errors were encountered: