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.
Better detection of poorly formed JSX (HTML)
See original GitHub issueNot sure what to do yet but would be great if we could validate templates in a way that we ensure the browser won’t mess with them when we instantiate them. Things like how browsers insert <tbody> if you omit it. Or the way certain elements aren’t allowed certain children. This is critical because it breaks walks during render/hydration.
Right now I just count the tags at runtime which is super rudimentary and it only runs in dev mode since we don’t want the additional code/overhead. In theory this can be done at compile time but I don’t know of any existing packages. Maybe failing that we could just develop something ourselves?
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (13 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
This is ok at least from our perspective. The only thing getting force fixed by the browser are the templates I think. Maybe there are exceptions still. But like the
<tbody>doesn’t happen if you just append a<tr>.https://github.com/MananTank/validate-html-nesting