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.
Nested script inside jsx tag is not parsed
See original GitHub issue<CodeView title={<span title={123}>2</span>}>for of as</CodeView>
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Adjacent JSX elements must be wrapped in an enclosing tag ...
javascript - Parse Error: Adjacent JSX elements must be wrapped in an enclosing tag - Stack Overflow. Stack Overflow for Teams – Start...
Read more >JSX In Depth - React
The first part of a JSX tag determines the type of the React element. Capitalized types indicate that the JSX tag is referring...
Read more >Code completion not working for nested JSX tags
Based on my experience, current behavior is wrong. I understand why code completions for methods and variables should not be enabled for HTML ......
Read more >remarkablemark/html-react-parser - GitHub
The parser converts an HTML string to one or more React elements. To replace an element with another element, check out the replace...
Read more >html react parser - Medium
The parser converts an HTML string to React element(s). ... Although <script> tags are parsed, react-dom does not render the contents.
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
I accidently closed the issue when #1345 was merged. But it was actually fixed in the next commit (cc80ccda8a2ec5565750ce67a2135b109748b5cd). A test for this specific use case was added in f0e6249e4f4417a7497792c0b9b8fcd133e9564e.
So it should be fixed now! 🎉
Note that we probably still won’t be able to handle infinite recursion (since JS regexps are not recursive), but at least this use case is handled!
Yes exactly! Both for the problem and code complication… Hope it would be resolved from prismjs side finally some day!
Thanks for your effort on making such a great tool!