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.

Sign up for GitHub

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

Jump to bottom

fix: make no-jest-import error message more accurate #1169

Closed
wants to merge 3 commits into from
Closed

fix: make no-jest-import error message more accurate #1169

wants to merge 3 commits into from

Commits on Jul 19, 2022

  1. fix: make no-jest-import error message more accurate 

    It isn't quite accurate to say that Jest doesn't export anything. It exports the `run` and `runCLI` functions, even though it isn't generally recommended to use them.

This commit updates the message to match the language in https://jestjs.io/docs/jest-object ("The `jest` object is automatically in scope within every test file").

I'll follow this commit with an update to the no-jest-import.md file too.
    @mmkal
    mmkal committed Jul 19, 2022
    Configuration menu
    Copy the full SHA
    a8d53e2 View commit details
    Browse the repository at this point in the history

  2. Update no-jest-import.md

    @mmkal
    mmkal committed Jul 19, 2022
    Configuration menu
    Copy the full SHA
    a8b77a5 View commit details
    Browse the repository at this point in the history

  3. Update no-jest-import.md

    @mmkal
    mmkal committed Jul 19, 2022
    Configuration menu
    Copy the full SHA
    70f07ad View commit details
    Browse the repository at this point in the history