projects option is not respected when only one project match

[samouss]

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. The projects 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

[thymikee]

Already fixed, see: #4117

[wtgtybhertgeghgtwtg]

With jest@22.4.3, the issue is still present. That snippet he linked is still in master, too.

[SimenB]

Missed this :( Let's consolidate in #7496

[github-actions]

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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.