`object-property-newline` with enhanced object literals
See original GitHub issueUsing the object-property-newline
rule in conjunction with an object containing only enhanced object literals written on the same line reports as an error, as expected. What I want is an option to allow for writing the props on the same line if it contains only enhanced object literals. Since those are defined outside the object it makes it kinda moot to write them on different lines.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:6
- Comments:14 (9 by maintainers)
Top Results From Across the Web
object-property-newline - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >ES6 in Action: Enhanced Object Literals
This article looks at what's possible with object literals in JavaScript, especially in the light of recent ECMAScript updates.
Read more >Enhanced Object Literals - Web Dev Simplified Blog
With these enhancements you can write code to create objects that is easier to read and more concise. In this article I will...
Read more >jsonc/object-property-newline
This rule permits you to restrict the locations of property specifications in object literals. You may prohibit any part of any property ...
Read more >object-property-newline (Rules) - Eslint 中文开发手册
This rule permits you to restrict the locations of property specifications in object literals. You may prohibit any part of any property ...
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 FreeTop 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
Top GitHub Comments
I’m 👍 and would potentially champion once I close some other issues.
I’m closing this issues because it looks like consensus couldn’t be reached. While we wish we could accommodate all requests, we have limited resources and do need to prioritize. We’ve found that issues failing to reach consensus after 21 days tend to never reach consensus, and as a team have decided to close such issues. This doesn’t mean the idea isn’t interesting or valuable, only that it’s not something the team can commit to at the moment.