-
Notifications
You must be signed in to change notification settings - Fork 2
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
chore: make react-hooks/exhaustive-deps eslint rule error vs. warn #950
Conversation
This pull request has been linked to Shortcut Story #40033: Enable react-hooks/exhaustive-deps for React projects. |
@bdow - there was never a lint step in CI for this project, so I added one. I didn't disable these existing errors:
Do you want me to disable them? Or do you (or someone else) want to look at it? |
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.
🎉
a3f614e
to
2dfbd52
Compare
2dfbd52
to
5e0489c
Compare
Let's disable them for now. If you don't mind, could you write a ticket and assign it to me I can take it from there. Thanks! |
Yep, can do. |
🎉 This PR is included in version 2.318.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
[sc-40033]
https://homeboundinc.slack.com/archives/C012SEYSQGG/p1694472845039779
I used a codemod to supress all existing errors:
I also used a simple regex replace to clean up the comments:
Then, finally, run
yarn lint:fix
(or commit to get the pre-commit hook) to run prettier.