Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Separate `quotes` rule for Object keys
See original GitHub issueCurrently, the quotes rule is applied to all strings.
Although, JS supports both single, double or no quotes for key names in Objects, JSON spec. explicitly states to use double quotes for keys.
To be consistent with JSON spec., I’d like to have my keys in double quotes, while other strings in single quotes.
I propose a new rule specifically for handling quotes in Object keys - key-quotes.
By default, it could very well inherit the quotes rule.
<bountysource-plugin>
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>
Issue Analytics
- State:
- Created 8 years ago
- Comments:13 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Don’t take this proposal as me wanting to champion this feature though. I’m not convinced this is a necessary enhancement. Just wanted to move discussion one way or another (it’s been sitting around without resolution for a long time).
I’m thinking this is best off as a custom rule for now. I don’t see a big need for this in core.