-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add Jest linting - Add lint to remind you not to leave in an exclusive/focused test #33
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the idea adding the rules.
Jest should be added here as well https://github.com/matrix-org/eslint-plugin-matrix-org/blob/main/index.js
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MadLittleMods can you update the branch?
Also it would be nice to have a JS SDK PR that previews the changes, if all the rules are applied. Adapting to code may take some time:
✖ 332 problems (209 errors, 123 warnings)
61 errors and 0 warnings potentially fixable with the `--fix` option.
(output for JS SDK using this branch with main
merged)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
Thanks for your work on the tests!
7a6fd4d
to
f430bfb
Compare
Thanks for wrangling a release here @weeman1337 😊 This is now part of |
Add Jest linting. Rules: https://github.com/jest-community/eslint-plugin-jest#rules
Spawning from matrix-org/matrix-js-sdk#2856 (comment) where I really only was after
jest/no-focused-tests
to remind you not to leave in an exclusive/focused test but it doesn't seem harmful to add the rest of the "recommended" ones. Hopefully we don't have to battle a pile of changes in our downstream repos to get usage adopted.References: