-
Notifications
You must be signed in to change notification settings - Fork 47.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTML characters are parsed (why?) #1177
Comments
That should definitely not be happening, but it seems like you're asking a question rather than having an actual issue. Quick testing on my side shows no issues, if you're having an issue it would be great if you could provide some code that reproduces the error. |
Well, I am using gulp-react that uses react-tools.
As the result of transformation I get this
|
Ah yes, React does not actually render it as straight HTML, so you cannot have HTML-entities in the strings. Is this an issue for you somehow or are you just curious? |
Yes, the issue was that my browser somehow set the encoding to 'ISO'. |
@onion-soup Ah, it's also worth knowing that you can do PS. Correct is |
Hi there,
Is it possible that react compiler turns html characters (like
<
) inside a React code into literal characters, when compiled, causing problems when opened in a browser.Is there a way to fix it?
The text was updated successfully, but these errors were encountered: