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

Enable no multiple empty lines rule #45

Merged
merged 2 commits into from
Mar 10, 2022

Conversation

rushatgabhane
Copy link
Member

Problem

PRs for Expensify/App often have extra unnecessary empty lines.
Some examples - Expensify/App#8059 (comment), Expensify/App#7660 (comment)

Solution

This PR 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

@rushatgabhane
Copy link
Member Author

Hmm, Melvin doesn't seem interested in this repo.

@luacmartins could you please give this a review whenever you can (should take 2 mins).
Thanks so much 🙇‍♂️

@luacmartins luacmartins self-requested a review March 10, 2022 16:09
Copy link
Contributor

@luacmartins luacmartins left a comment

Choose a reason for hiding this comment

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

LGTM! We should make sure to fix all the errors when bumping this in App.

@luacmartins luacmartins merged commit dcee44e into Expensify:main Mar 10, 2022
@rushatgabhane
Copy link
Member Author

Thanks, I'm on it

@rushatgabhane
Copy link
Member Author

rushatgabhane commented Mar 10, 2022

@luacmartins sorry for the trouble, but if I'm not wrong, this needs to be published to npm internally.
Could you please publish v2.0.24 to npm? Thanks

https://github.com/Expensify/eslint-config-expensify#after-pr-is-merged

@luacmartins
Copy link
Contributor

Thanks @rushatgabhane! New version is available in npm!

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.

2 participants