fix(android): fix fadeDuration=0 not working w/ props 2.0 diffing #55521
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:
In our app we are using the props 2.0 diffing mechanism (ie
getDiffPropsin cpp).I noticed that our
<Image source={...} fadeDuration={0} />were still showing with the default 300ms fade duration.The issue is that we instantiate the
fadeDurationin cpp with a default value of0:react-native/packages/react-native/ReactCommon/react/renderer/components/image/ImageProps.h
Line 40 in 4356259
and then in the props diff implementation when comparing our prop value of
0against the default, it will not be added to the final props, thus never set in the native image view:react-native/packages/react-native/ReactCommon/react/renderer/components/image/ImageProps.cpp
Lines 273 to 275 in 4356259
The native image view uses a default value of
-1so i thought to use the same here:react-native/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/views/image/ReactImageView.kt
Line 104 in 4356259
Another solution could be to type the
fadeDurationasstd::optional, let me know what you preferChangelog:
[ANDROID] [FIXED] - Image fadeDuration=0 not working with props 2.0 enabled
Test Plan:
You can enable the props 2.0 feature flags in the RNTesterApp and check the image example!