Match numbers and string to element-valued properties #6028
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
#13216 Bundle Size — 62.37MiB (~+0.01%).
Warning Bundle contains 51 duplicate packages – View duplicate packages Bundle metrics
|
| Current #13216 |
Baseline #13214 |
|
|---|---|---|
 Initial JS |
45.43MiB(~+0.01%) |
45.43MiB |
 Initial CSS |
0B |
0B |
 Cache Invalidation |
21.58% |
23.23% |
| Chunks |
30 |
30 |
| Assets |
33 |
33 |
| Modules |
4313 |
4313 |
| Duplicate Modules |
525 |
525 |
| Duplicate Code |
31.79% |
31.79% |
| Packages |
450 |
450 |
| Duplicate Packages |
51 |
51 |
Bundle size by type 2 changes 1 regression 
1 improvement
| Current #13216 |
Baseline #13214 |
|
|---|---|---|
| JS |
62.35MiB (~+0.01%) |
62.35MiB |
| HTML |
11.16KiB (-0.33%) |
11.2KiB |
Bundle analysis report Branch feature/jsx-match-string-number Project dashboard
seanparsons
approved these changes
Jul 1, 2024
ruggi
approved these changes
Jul 1, 2024
liady
pushed a commit
that referenced
this pull request
Dec 13, 2024
## Problem If there's no annotation for a component property, we only treat JSX elements as matching values for render props, even though strings and numbers would be valid elements children as well. ## Fix If we detect a render prop, the matching code treats strings and numbers as matching as well. #5979
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.
Problem
If there's no annotation for a component property, we only treat JSX elements as matching values for render props, even though strings and numbers would be valid elements children as well.
Fix
If we detect a render prop, the matching code treats strings and numbers as matching as well.
#5979