-
Notifications
You must be signed in to change notification settings - Fork 26.8k
Implicit return + single expression #472
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
Conversation
README.md
Outdated
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.
Let's make this 8.3 and have the good bad examples nestled up underneath.
|
Couple of comments, love the added clarity. Thanks @tomekwi! |
|
Thanks for the comments @hshoff 👍 . I can come back to this tomorrow morning, European time. Until then! |
|
🏁 Sorry for scattering the changes over so many commits. I can rebase if you don’t mind losing your line comments @hshoff. |
|
🏆 |
Implicit return + single expression
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.
This change doesn't hold the original intent of the text where parens are ok to omit only when you're using implicit return, otherwise they're required. cc @ljharb
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.
Let's please revert this text then, and also ensure the eslint plugin enforces it.
Fixes #438.
I’ve upgraded the note about argument parens to a new rule – it reads better this way.