feature: helpful error message when child DOM not found #148
Conversation
This file contains 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
saibotsivad
force-pushed
the
feature/helpful-error-message
branch
2 times, most recently
from
1f21097
to
cd6ab2d
Compare
saibotsivad
force-pushed
the
feature/helpful-error-message
branch
from
cd6ab2d
to
4d89557
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If you forget to put a child node in, for example in Svelte it would be forgetting to put the
uiViewelement, the error that gets thrown is rather cryptic.The exact error depends on the renderer exactly, but for example in Svelte it looks like this:
Instead of throwing a cryptic error, we can reject with an error that gets bubbled out to
stateChangeError.