This repository has been archived by the owner on Jul 28, 2023. It is now read-only.
Handle missing class attribute inside wp-class
#149
Merged
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.
What
Fixes a bug while hydrating
wp-class
directives. It happens when theclass
attribute is not defined―something that occurs when no class is server-side rendered. E.g., the following HTMLcurrently throws this error:
Also, when the button is clicked, the application crashes.
Why
Directives should take care of those attributes they affect.
In this case, developers shouldn't be forced to write an empty class to make the
wp-class
directive work as expected.How
Simply using an empty string when
element.props.class
is undefined.