Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign uppadded-blocks for classes and switches #610
Comments
This comment has been minimized.
This comment has been minimized.
|
@caesarsol Yes, you're right. It looks like these additional cases were added to eslint but aren't covered by the current "never" setting. We'll add this in standard v9. |
feross
added this to the
standard v9 milestone
Sep 10, 2016
feross
added
the
enhancement
label
Sep 10, 2016
This comment has been minimized.
This comment has been minimized.
|
Perfect, thanks! |
feross
added a commit
to standard/eslint-config-standard
that referenced
this issue
Feb 9, 2017
This comment has been minimized.
This comment has been minimized.
|
This will be part of standard v9. No ecosystem impact. |
feross
closed this
Feb 9, 2017
feross
added a commit
to standard/eslint-config-standard
that referenced
this issue
Feb 9, 2017
lock
bot
locked as resolved and limited conversation to collaborators
May 10, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
caesarsol commentedSep 2, 2016
•
edited
As of now, the
padded-blocksrule is configured as:Since:
And this implies that in classes and switch statements the never-padded-blocks is not enforced, wouldn't it be coherent to modify the rule as this?
Here is the reference: http://eslint.org/docs/rules/padded-blocks#classes