-
Notifications
You must be signed in to change notification settings - Fork 26
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
Use eslint-config-stripes #42
Use eslint-config-stripes #42
Conversation
} | ||
return false; |
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.
Is this a linting rule that got triggered?
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.
Yes https://eslint.org/docs/rules/no-else-return
I have mixed feelings about that rule.
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.
Yeah, these days I favor symmetry over efficiency when given a choice
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.
As a general policy, we want ESLint to be our servant, not our master. Bondage-and-discipline rules like no-nested-ternary and no-plusplus can go, with no period of mourning required. no-else-return definitely belongs in this category!
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.
Re: Jenkins build failures: is it running into a cached npm registry or something? |
Right. npmjs.org is cached. The builds passes now. |
Switches to using shared FOLIO eslint config: https://github.com/folio-org/eslint-config-stripes