This repository was archived by the owner on Jan 28, 2026. It is now read-only.
🐛 Catch removeChild error use semantic node instead of text node#309
Merged
asim-shrestha merged 1 commit intoreworkd:mainfrom Apr 22, 2023
Merged
Conversation
|
@l2hyunwoo is attempting to deploy a commit to the reworkd Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ref: facebook/react#11538 (comment)
fixed: #212
Additional Question) There's another workaround that if removeChild will cause error keep child node and make not crush. Is below code useful to this situation?