We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
use-test
t.context
The AVA documentation recommends to to type t.context as follow:
import anyTest, {TestInterface} from 'ava'; const test = anyTest as TestInterface<{foo: string}>;
However importing AVA as anyTest instead of test triggers the use-test rule.
anyTest
test
I can make a PR but I don't know what the best solution is. Any suggestion?
The text was updated successfully, but these errors were encountered:
Could we check if it's a TypeScript file and allow anyTest as a name then? I think the rule context exposes the source file name.
Sorry, something went wrong.
Heh, I've been using ava as the default import. But anyTest is still fine.
ava
Thanks @pvdlg, 10.1.0 is now available 🎊
Successfully merging a pull request may close this issue.
The AVA documentation recommends to to type
t.context
as follow:However importing AVA as
anyTest
instead oftest
triggers theuse-test
rule.I can make a PR but I don't know what the best solution is. Any suggestion?
The text was updated successfully, but these errors were encountered: