You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR fixes an issue with the handling of null values in component props when default props are set. Previously, the loose equality check (==) would treat null values the same as undefined, causing default props to override explicitly passed null values. The fix changes these checks to strict equality (===), ensuring that null values are preserved as intended.
The change applies to:
createElement
cloneElement
jsx-runtime
Test cases were added to verify proper handling of null prop values with defaultProps in all affected locations.
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
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.
Fixes #4774
This PR fixes an issue with the handling of null values in component props when default props are set. Previously, the loose equality check (==) would treat null values the same as undefined, causing default props to override explicitly passed null values. The fix changes these checks to strict equality (===), ensuring that null values are preserved as intended.
The change applies to:
Test cases were added to verify proper handling of null prop values with defaultProps in all affected locations.