[JSX] Do not convert html-escaped entities to their prettier forms
See original GitHub issueMost HTML entity names & numbers are converted to their literal form.
Seems
<
>
are the only exceptions?
(
escaping was fixed in #557)
Is this expected?
<span>
// not converted
 
< <
> >
// converted
& &
" "
' '
á á
</span>
turns into
<span>
// not converted
< <
> >
// converted
& &
" "
' '
á á
</span>;
Thanks.
Issue Analytics
- State:
- Created 7 years ago
- Comments:18 (7 by maintainers)
Top Results From Across the Web
How to fix this violation of this 'react/no-unescaped-entitie' of ...
One way to fix the react/no-unescaped-entities error is by assigning the text with the escape character in it to a variable and then ......
Read more >Replace Html Entities : r/reactjs - Reddit
I'm fetching data from "Open Trivia DB" for a quiz app. The json data that comes has i'm not sure about the name...
Read more >JSX Gotchas | React
HTML Entities If you want to display an HTML entity within dynamic content, you will run into double escaping issues as React...
Read more >Rationale - Prettier
JSX takes its roots from HTML, where the dominant use of quotes for attributes is double quotes. ... Prettier maintains the way your...
Read more >Escaping Special Characters < JavaScript | The Art of Web
If you have a string to decode, use the buttons on the right instead. INPUT: The function you select will be applied to...
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
https://github.com/babel/babylon/pull/344 and https://github.com/babel/babel/pull/5256 have been approved – I am told they should be merged into Babel 7.0.
@MrEfrem this should have been fixed by #1165 🤞.