Warning "Whitespace text nodes cannot appear as a child of <tbody>"

Open

#132 opened on May 4, 2022 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: react, typescript
Domain: devtools, frontend

Research direction

Reproduce the warning with version 4.1.0 and inspect the PanelTable entry in the @hookform_devtools.js stack trace, then trace it back to the corresponding source component. Confirm the issue is addressed when the tbody warning no longer appears in the reproduction.

Written by the indexing model from the issue text.

Description

bug

I'm able to reproduce it with version 4.1.0

Warning: validateDOMNesting(...): Whitespace text nodes cannot appear as a child of <tbody>. Make sure you don't have any extra whitespace between tags on each line of your source code.
tbody
table
withEmotionCache2/<@http://localhost:3000/node_modules/.vite/deps/@hookform_devtools.js?v=6ea3fd1b:1935:45
PanelTable@http://localhost:3000/node_modules/.vite/deps/@hookform_devtools.js?v=6ea3fd1b:2618:19
section
PanelChildren@http://localhost:3000/node_modules/.vite/deps/@hookform_devtools.js?v=6ea3fd1b:2694:16
div
div
Panel@http://localhost:3000/node_modules/.vite/deps/@hookform_devtools.js?v=6ea3fd1b:2729:17
div
div
Animate2@http://localhost:3000/node_modules/.vite/deps/@hookform_devtools.js?v=6ea3fd1b:88:178
DevToolUI@http://localhost:3000/node_modules/.vite/deps/@hookform_devtools.js?v=6ea3fd1b:2806:17
r@http://localhost:3000/node_modules/.vite/deps/@hookform_devtools.js?v=6ea3fd1b:676:12
DevTool@http://localhost:3000/node_modules/.vite/deps/@hookform_devtools.js?v=6ea3fd1b:2825:17
form
section
...
ErrorHandler@http://localhost:3000/src/routes/Error.tsx:37:29 [react_devtools_backend.js:3973:25](moz-extension://669074cd-27cf-4149-a4d2-4519db47042e/build/react_devtools_backend.js)

Dominant language: TypeScript
Stars: 670
Forks: 55
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.