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
padded-blocks for classes and switches #610
Labels
Milestone
Comments
@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. |
Perfect, thanks! |
feross
added a commit
to standard/eslint-config-standard
that referenced
this issue
Feb 9, 2017
Currently, we disallow empty lines at the beginning and ending of block statements (except switch statements and classes). This rule change also applies this rule to switch statements and classes. Fixes: standard/standard#610
This will be part of standard v9. No ecosystem impact. |
feross
added a commit
to standard/eslint-config-standard
that referenced
this issue
Feb 9, 2017
Currently, we disallow empty lines at the beginning and ending of block statements (except switch statements and classes). This rule change also applies this rule to switch statements and classes. Fixes: standard/standard#610
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As of now, the
padded-blocks
rule 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
The text was updated successfully, but these errors were encountered: