New rule: padded-object
See original GitHub issuePlease describe what the rule should do:
seems like we have been lack of linting blank lines in multiline object properties.
What category of rule is this? (place an “X” next to just one item)
[x] stylistic
Provide 2-3 code examples that this rule will warn about:
/* padded-object: ["error", "never"]*/
var foo = {
bar: 0
}
/* padded-object: ["error", "both"]*/
var foo = {
bar: 0
}
Why should this rule be included in ESLint (instead of a plugin)?
This rule seems like a fairly universal and common requirement. It meets all the core rule guidelines.
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Proposed rule: Prohibition Against Fraud, Manipulation, or ...
proposing for comment a rule under the Securities Exchange Act of 1934 (“Exchange Act”), which would be a new rule designed to prevent...
Read more >Altering a padded object after having bent it - FreeCAD Forum
After having created a body with and laying out the holes and slots and then bending it, I need to alter the main...
Read more >TITLE 48 - West Virginia Secretary of State
Rule governing the safety training program for prospective surface coal miners in West Virginia. ... State and federal laws that pertain to the...
Read more >A model performance standard for guardrails - GovInfo
Nonetheless, it is not the intent of this Criterion to rule out consideration ... in accordance with the applicable provisions of the latest...
Read more >Intel® oneAPI DPC++/C++ Compiler Release Notes - 英特尔
Added support for the new FPGA attribute [[intel::fpga_pipeline(N)]] for loop ... Added a new rule for naming C++ identifiers in the SYCL project....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m wondering if we should just add this into
padded-blocks
. (Yes, we’re completely stretching the definition of what a “block” is, but the rule already does that by including class bodies and switch statements.)Ideally, if an issue is open for long enough, it gets reviewed by the team. However, we get a lot of feature requests and we wouldn’t realistically be able to implement and maintain all of them, so we err on the side of not accepting proposals after awhile unless there is a clear consensus in favor accepting them. In this case, there wasn’t a strong consensus one way or the other, so I closed the issue.
If this is still something you’d like to advocate for, feel free to open a new issue.