-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
projects option is not respected when only one project match #5866
Comments
Already fixed, see: #4117 |
With |
Missed this :( Let's consolidate in #7496 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Do you want to request a feature or report a bug?
BUG
What is the current behavior?
When we use the
projects
option from the configuration file with only one project match Jest will bypass the project configuration and resolve all the test files from the root. The issue only happen with configuration file, when the option is provided to the CLI there is no issue. Here you can find an example.What is the expected behavior?
Respect the
projects
option provided from the configuration file even with a single project.Relevant files:
The issue seems to come from the
jest-cli
package. Theprojects
option is not respected because this condition (see below) is not executed when only one package match.https://github.com/facebook/jest/blob/1a487c1803124c594bdd86ee24b5949025660bc3/packages/jest-cli/src/cli/index.js#L248-L276
The text was updated successfully, but these errors were encountered: