-
Notifications
You must be signed in to change notification settings - Fork 14.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
style: eslint curly rule #11913
style: eslint curly rule #11913
Conversation
Codecov Report
@@ Coverage Diff @@
## master #11913 +/- ##
==========================================
+ Coverage 66.04% 67.60% +1.55%
==========================================
Files 927 928 +1
Lines 45016 45053 +37
Branches 4309 4309
==========================================
+ Hits 29730 30457 +727
+ Misses 15151 14493 -658
+ Partials 135 103 -32
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
Thank you!
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.
could you add this rule for ts/tsx files too?
As a followup in another PR, we should fix this file so that the TS config extends from the JS one probably
Hah, I did add the ts one, but forgot to push it! Incoming! The follow-up PR extending TS from JS makes perfect sense. I'll get to that sometime if nobody beats me to it ;) |
Hmm, I thought ESLint |
SUMMARY
On a recent PR, I had a simple if/else, sans-curlies, and @ktmud asked me to put them in. Seemed like a reasonable style call, so I'm adding a lint rule to make sure we're more consistent about this going forward!
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TEST PLAN
ADDITIONAL INFORMATION