Fix fastAddProperties to properly nullify style props #30334
Merged
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
javache
approved these changes
Jul 15, 2024
Comment on lines
+63
to
+70
| it('should nullify previously defined style prop that is subsequently set to null or undefined', () => { | ||
| expect( | ||
| create({style: [{a: 0}, {a: undefined}]}, {style: {a: true}}), | ||
| ).toEqual({a: null}); | ||
| expect(create({style: [{a: 0}, {a: null}]}, {style: {a: true}})).toEqual({ | ||
| a: null, | ||
| }); | ||
| }); |
There was a problem hiding this comment.
Is fastAddProperties tested in this codepath? Can we run these tests with enableAddPropertiesFastPath enabled?
There was a problem hiding this comment.
Yes, with
yarn test packages/react-native-renderer -r=xplat --variant=true
dmytrorykun
force-pushed
the
fix-fastAddProps
branch
from
25ff830
to
b0d469e
Compare
github-actions bot
pushed a commit
that referenced
this pull request
Jul 15, 2024
## Summary
This PR fixes the `fastAddProperties` function. Now it nullifies a prop
if it was defined in one of the items of a style array, but then set to
`undefined` or `null` in one of the subsequent items. E.g. `style:
[{top: 0}, {top: undefined}]` should evaluate to `{top: null}`. Also
added a test case for that.
## How did you test this change?
```
yarn test packages/react-native-renderer -r=xplat --variant=false
yarn test packages/react-native-renderer -r=xplat --variant=true
yarn flow native
```
DiffTrain build for commit f510ece.
felixshiftellecon
added a commit
to felixshiftellecon/react
that referenced
this pull request
Jul 24, 2024
## Summary
This PR fixes the `fastAddProperties` function. Now it nullifies a prop
if it was defined in one of the items of a style array, but then set to
`undefined` or `null` in one of the subsequent items. E.g. `style:
[{top: 0}, {top: undefined}]` should evaluate to `{top: null}`. Also
added a test case for that.
## How did you test this change?
```
yarn test packages/react-native-renderer -r=xplat --variant=false
yarn test packages/react-native-renderer -r=xplat --variant=true
yarn flow native
```
felixshiftellecon
added a commit
to felixshiftellecon/react
that referenced
this pull request
Jul 24, 2024
## Summary
This PR fixes the `fastAddProperties` function. Now it nullifies a prop
if it was defined in one of the items of a style array, but then set to
`undefined` or `null` in one of the subsequent items. E.g. `style:
[{top: 0}, {top: undefined}]` should evaluate to `{top: null}`. Also
added a test case for that.
## How did you test this change?
```
yarn test packages/react-native-renderer -r=xplat --variant=false
yarn test packages/react-native-renderer -r=xplat --variant=true
yarn flow native
```
This was referenced Jul 25, 2024
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.
Summary
This PR fixes the
fastAddPropertiesfunction. Now it nullifies a prop if it was defined in one of the items of a style array, but then set toundefinedornullin one of the subsequent items. E.g.style: [{top: 0}, {top: undefined}]should evaluate to{top: null}. Also added a test case for that.How did you test this change?