-
Notifications
You must be signed in to change notification settings - Fork 53
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: upgrade eslint config deps #4977
chore: upgrade eslint config deps #4977
Conversation
Size Change: +2 B (0%) Total Size: 13.4 MB ℹ️ View Unchanged
|
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
@@ -88,7 +88,9 @@ | |||
"testing-library/custom-renders": "off", | |||
"testing-library/custom-queries": "off", | |||
"testing-library/no-node-access": "off", | |||
"testing-library/render-result-naming-convention": "off" | |||
"testing-library/render-result-naming-convention": "off", | |||
|
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.
why this empty line ?
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.
To be homogeneous with existing format for how to write rules : there is a paragraph for each "rule provider" (see above)
What is the problem this PR is trying to solve?
Upgrade deps of scripts-config-eslint to handle.
What is the chosen solution to this problem?
Do upgrade and manage breaking changes if necessary.
Please check if the PR fulfills these requirements
yarn changeset
to a request a release from the CI if wanted.[ ] This PR introduces a breaking change