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

Resolving to jest executable defaults to first folder in current workspace | automatically detect workspace subproject to find jest executable #23

Closed
PBug90 opened this issue May 23, 2019 · 4 comments
Labels

Comments

@PBug90
Copy link
Contributor

PBug90 commented May 23, 2019

When using a workspace with multiple projects, the test runner executes jest from the first folder in the current workspace if no explicit jest executable path had been configured:

return join(vscode.workspace.workspaceFolders[0].uri.fsPath, jestDirectoy);

Is there any way to change that so it detects the correct workspace project that the file of the currently executed test resides in?

@firsttris firsttris added the bug label May 23, 2019
@firsttris
Copy link
Owner

there shoud be a way of getting the active workspaceFolder or the workpaceFolder number/index.

in the documentation if found getWorkspaceFolder but probably thats not what we need here ..

https://code.visualstudio.com/api/references/vscode-api

@PBug90
Copy link
Contributor Author

PBug90 commented May 27, 2019

Added a PR: #25

@firsttris
Copy link
Owner

thx!

@firsttris
Copy link
Owner

fixed

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

No branches or pull requests

2 participants