Fix className patch not applied to props#2279
Merged
Merged
Conversation
|
Size Change: -1 B Total Size: 38.2 kB
ℹ️ View Unchanged
|
JoviDeCroock
approved these changes
Jan 25, 2020
Member
Author
|
@JoviDeCroock unfortunately not, but I think I know what's going on. |
65c4ca7 to
dfc7f36
Compare
porfirioribeiro
pushed a commit
to porfirioribeiro/preact
that referenced
this pull request
Feb 3, 2020
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 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.
This error was caused by our
classNamepatch being applied to the wrongpropsreference. Whenever a component is in play like with most CSS-in-JS solutions and we attempt to normalizepropswe'll create a new reference.preact/compat/src/render.js
Line 111 in 8164289
A few lines later we attached the
classNamepatch, but we didn't update the reference of ourpropsvariable to point to the new object.Since the order of our normalizations isn't important, the easiest fix is to move the
classNamecheck before the other wherepropswill be assigned a new variable.Fixes #2275