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

Error: Expected a single value for option --exclude <glob>, received ["a/*", "b/*"] #5779

Closed
4 tasks done
fregante opened this issue May 26, 2024 · 1 comment · Fixed by #5782
Closed
4 tasks done
Labels
p3-minor-bug An edge case that only affects very specific usage (priority)

Comments

@fregante
Copy link
Contributor

Clear and concise description of the problem

Until Vitest 1.2 I was able to use two --exclude globs, but this feature some inexplicably removed. I'm using this to split certain tests on CI so these globs cannot be part of the static configuration.

The command I'm running is:

vitest --run --exclude build/features* --exclude **/selectors*

Suggested solution

Please restore the ability to call --exclude multiple times

Alternative

No response

Additional context

No response

Validations

@hi-ogawa
Copy link
Contributor

hi-ogawa commented May 26, 2024

Probably this got unintentionally broken when cli parsing is reworked. We can put back array: true somewhere like the other issue we had:

@hi-ogawa hi-ogawa added p3-minor-bug An edge case that only affects very specific usage (priority) and removed enhancement: pending triage labels May 26, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jun 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
p3-minor-bug An edge case that only affects very specific usage (priority)
Projects
None yet
2 participants