-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[No QA] Upgrade eslint-config-expensify to enable no-multiple-empty-lines rule #8068
[No QA] Upgrade eslint-config-expensify to enable no-multiple-empty-lines rule #8068
Conversation
package.json
Outdated
@@ -151,7 +151,7 @@ | |||
"electron-notarize": "^1.0.0", | |||
"electron-reloader": "^1.2.1", | |||
"eslint": "^7.6.0", | |||
"eslint-config-expensify": "2.0.23", | |||
"eslint-config-expensify": "^2.0.24", |
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.
Should we prevent using ^
here? I think if we add new lint rule then it will fail for others if they do fresh npm i, unless all errors are fixed beforehand.
Just my thought. What do you think?
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.
Oh yeah, good point.
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
Thank you for fixing this!! |
My pleasure. |
🚀 Deployed to staging by @MonilBhavsar in version: 1.1.43-0 🚀
|
🚀 Deployed to production by @roryabraham in version: 1.1.43-2 🚀
|
PRs for Expensify/App often have extra unnecessary empty lines.
As a follow up to Expensify/eslint-config-expensify#45, this PR upgrades
eslint-config-expensify
tov2.0.24
This enables the
no-multiple-empty-lines
rule, which will throw a lint error when more than 1 consecutive empty line is used.Reference: https://eslint.org/docs/rules/no-multiple-empty-lines
Fixed Issues
NA
Tests
npm run lint
PR Review Checklist
Contributor (PR Author) Checklist
main
### Fixed Issues
section abovesrc/languages/*
files (if applicable)Styling.md
) for all style edits I madeSTYLE.md
)Avatar
, I verified the components usingAvatar
are working as expected)main
branch)PR Reviewer Checklist
main
### Fixed Issues
section abovesrc/languages/*
files (if applicable)STYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)main
branch)