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
pattern
CLI option Path Expansion
#3206
Comments
Related to this:
|
Do you have a stack trace for that error? The pattern is resolved against to the current working directory and then made relative against the project directory: Line 419 in 6398772
However it doesn't look like that expands the I'd expect absolute paths to be resolved, however (as I recall) AVA cannot run test files outside of the project directory. Perhaps that could be communicated better. Local paths really should work. |
I'll be doing some additional testing today for a related moon issue and will grab a stack trace then. |
Please provide details about:
pnpm exec ava ~/code/tests
This results in an error:
Expected pattern to be a non-empty string
The error is both incorrect and unfortunate. The
pattern
passed was not empty,ava
just didn't know what to do with it.Oodles of tertiary tooling will provide paths with a leading tilde. However correct or incorrect that is, it would be useful for local tooling to be able to leverage a tilde as a home directory path.
Execute a
resolve
on the passed pattern if it doesn't match any of the other expected shapes, or begins with a tilde.The text was updated successfully, but these errors were encountered: