Stuck on an issue?
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.
"Single quote" property not working as expected
See original GitHub issueI currently have the “Single Quote” property in Atom set to true, however when I format the code using prettier, it is changing all single quotes to double quotes.
Formatting code:
Anyone else experiencing this or did I screw something up somewhere?
Issue Analytics
- State:
- Created 7 years ago
- Comments:5
Top Results From Across the Web
SPRING: Single quote not working in .properties file
I add single quote in both end of the value to ensure spaces are being escaped however it is being rendered as it...
Read more >Bug when single quote/apostrophe in property-set description
Solved: We came across a bug, because of which we were not able to add or remove our PCF control from the Grid....
Read more >Single Quote not getting replaced with Blank in lightning
I have an expression and I am trying to replace all single quote with blank but when I try to save my controller.js...
Read more >quotes - ESLint - Pluggable JavaScript Linter
This rule enforces the consistent use of either backticks, double, or single quotes. Options. This rule has two options, a string option and...
Read more >Why do I need to escape the last single quote in ... - Super User
IMHO, it is a bug in PowerShell parser. When in statement parse mode, it first try to interpret first thing as BareWord string...
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
Yep, since JSX was designed to be similar to HTML, the convention is to use double quotes for JSX attributes.
@jjwyse I think this is an issue relating to Prettier itself as it’s treating JSX attributes specially. You will notice that Prettier is not changing the single quotes at the top in your imports, so it is respecting the option that the atom plugin has set.