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.

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

Merged
merged 5 commits into from
Mar 11, 2022
Merged

[No QA] Upgrade eslint-config-expensify to enable no-multiple-empty-lines rule #8068

merged 5 commits into from
Mar 11, 2022

Conversation

rushatgabhane
Copy link
Member

@rushatgabhane rushatgabhane commented Mar 10, 2022

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 to v2.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

  1. Run npm run lint
  2. Verify that there are no lint errors.
  • Verify that no errors appear in the JS console

PR Review Checklist

Contributor (PR Author) Checklist

  • I verified the PR has a small number of commits behind main
  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I clearly indicated the environment tests should be run in (Staging vs Production)
  • I wrote testing steps that cover success & fail scenarios (if applicable)
  • I included screenshots or videos for tests on all platforms
  • I ran the tests & veryfy they passed on:
    • iOS / native
    • Android / native
    • iOS / Safari
    • Android / Chrome
    • MacOS / Chrome
    • MacOS / Desktop
  • I verified there are no console errors related to changes in this PR
  • I followed proper code patterns (see Reviewing the code)
    • I added comments when the code was not self explanatory
    • I put all copy / text shown in the product in all src/languages/* files (if applicable)
    • I followed proper naming convention for platform-specific files (if applicable)
    • I followed style guidelines (in Styling.md) for all style edits I made
    • I followed the JSDocs style guidelines (in STYLE.md)
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I corroborated the UI performance was not affected (the performance is the same than main branch)
  • If I created a new component I verified that a similar component doesn't exist in the codebase

PR Reviewer Checklist

  • I verified the PR has a small number of commits behind main
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the testing environment is mentioned in the test steps
  • I verified testing steps cover success & fail scenarios (if applicable)
  • I checked that screenshots or videos are included for tests on all platforms
  • I verified tests pass on all platforms & I tested again on:
    • iOS / native
    • Android / native
    • iOS / Safari
    • Android / Chrome
    • MacOS / Chrome
    • MacOS / Desktop
  • I verified there are no console errors related to changes in this PR
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified comments were added when the code was not self explanatory
    • I verified any copy / text shown in the product was added in all src/languages/* files (if applicable)
    • I verified proper naming convention for platform-specific files was followed (if applicable)
    • I verified style guidelines were followed
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components are not impacted by changes in this PR (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified the UI performance was not affected (the performance is the same than main branch)
  • If a new component is created I verified that a similar component doesn't exist in the codebase

@rushatgabhane rushatgabhane requested a review from a team as a code owner March 10, 2022 19:40
@MelvinBot MelvinBot requested review from MonilBhavsar and removed request for a team March 10, 2022 19:41
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",
Copy link
Contributor

@MonilBhavsar MonilBhavsar Mar 11, 2022

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?

Copy link
Member Author

@rushatgabhane rushatgabhane Mar 11, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh yeah, good point.

@MonilBhavsar MonilBhavsar merged commit 2ae0b89 into Expensify:main Mar 11, 2022
@OSBotify
Copy link
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@AndrewGable
Copy link
Contributor

Thank you for fixing this!!

@rushatgabhane
Copy link
Member Author

My pleasure.

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by @MonilBhavsar in version: 1.1.43-0 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@OSBotify
Copy link
Contributor

🚀 Deployed to production by @roryabraham in version: 1.1.43-2 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants