fix: getting vdom prop when vdom is not ready yet #66
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.
In my app something weird started to happen. I got this error message:
This have been happening to me when I was using my web component like that:
The weird thing is that removing the
value
attribute fixes it. Also any other attribute works just fine and also using this component in some other place of the app also works fine (even with thevalue
attribute set).For some unknown reason preact (or something else?) is trying to read the property of a component before the vdom is there, that's why we need to check for vdom existance (just like it's done in the
set
function).