docs: explain useNativeAnimations
for use cases
#2339
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.
Description
In cases where users use
LayoutAnimation
to smooth transitions upon swiping an item (e.g. perhaps swipe left deletes this Swipeable from a list), the non-open version of the Swipeable will be animated out (as opposed to the open version). This ends up looking bad/amatuer. Turns out this can be fixed by simply settinguseNativeAnimations
to false in those cases so that RN'sLayoutAnimation
shows the opened version of the Swipeable exiting.Test plan
View doc markdown