@cypress/grep prints warning if nothing is being grepped

[gofr]

Current behavior

1. Install the plugin and enable the grepFilterSpecs feature (as described in the README).
2. Run Cypress without doing any grepping at all.

Cypress prints the warning:

grep and/or grepTags has eliminated all specs

Desired behavior

Cypress does not print any warning.

Cause of the bug:

1. The greppedSpecs variable is initialized to an empty array here:

   cypress/npm/grep/src/plugin.js

   Line 78 in 12f9e8a

   let greppedSpecs = []

2. This variable is only updated when either grep or grepTags is defined. That means that it remains an empty array if no grepping is being done.
3. On this line the code then checks if there were any grepped specs:

   cypress/npm/grep/src/plugin.js

   Line 142 in 12f9e8a

   if (greppedSpecs.length) {

4. And then the bug is caused by the else here:

   cypress/npm/grep/src/plugin.js

   Line 144 in 12f9e8a

   } else {

If we did no grepping at all, we still go into that else and print a warning. That else should probably be changed to:

else if (grep || grepTags)

Test code to reproduce

See analysis above.

Cypress Version

10.10.0

Node version

N/A

Operating System

N/A

Debug Logs

No response

Other

No response