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
Introduced in Jest 24 (see this blog post), it seems like we could support a rule that would prefer the following:
test.todo('i need to write this test')
instead of:
test('i need to write this test') // and/or test('i need to write this test', () => {})
Haven't thought much about specifics, rule naming, etc. Just came here from the Jest 24 blog post and wanted to jot this down.
The text was updated successfully, but these errors were encountered:
Hi. Can I work on this?
Sorry, something went wrong.
Yeah, go for it!
It should also warn against test.skip('asdasdad', () => {})
test.skip('asdasdad', () => {})
0933d82
chore(release): 22.2.0 [skip ci]
13b7c98
# [22.2.0](v22.1.3...v22.2.0) (2019-01-29) ### Features * **rules:** add prefer-todo rule ([#218](#218)) ([0933d82](0933d82)), closes [#217](#217)
804c9a8
# [22.2.0](jest-community/eslint-plugin-jest@v22.1.3...v22.2.0) (2019-01-29) ### Features * **rules:** add prefer-todo rule ([#218](jest-community/eslint-plugin-jest#218)) ([abe1bfd](jest-community/eslint-plugin-jest@abe1bfd)), closes [#217](jest-community/eslint-plugin-jest#217)
No branches or pull requests
Introduced in Jest 24 (see this blog post), it seems like we could support a rule that would prefer the following:
instead of:
Haven't thought much about specifics, rule naming, etc. Just came here from the Jest 24 blog post and wanted to jot this down.
The text was updated successfully, but these errors were encountered: