Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[LA] Replace Layout Transitions example #6151

Merged

Conversation

patrycjakalinska
Copy link
Collaborator

@patrycjakalinska patrycjakalinska commented Jun 21, 2024

We replaced Default Layout Transition with refreshed example.

Before:
image

After:

Screen.Recording.2024-06-21.at.13.22.39.mov

@patrycjakalinska patrycjakalinska changed the title Replace Layout Transitions example [LA] Replace Layout Transitions example Jun 21, 2024
Copy link
Member

@piaskowyk piaskowyk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just two small things, but apart from that, it is ready to merge 👍

@piaskowyk piaskowyk mentioned this pull request Jun 28, 2024
@patrycjakalinska patrycjakalinska force-pushed the @patrycjakalinska/replace-layout-transition-example branch from e454c2e to d0bf50c Compare June 28, 2024 11:36
@patrycjakalinska patrycjakalinska added this pull request to the merge queue Jul 1, 2024
Merged via the queue into main with commit 8136d77 Jul 1, 2024
5 checks passed
@patrycjakalinska patrycjakalinska deleted the @patrycjakalinska/replace-layout-transition-example branch July 1, 2024 08:02
github-merge-queue bot pushed a commit that referenced this pull request Jul 1, 2024
## Summary

This PR aims to fix some unexpected behaviour during `FadingTransition`.

| before | after |
| --- | --- |
| <video
src="https://github.com/software-mansion/react-native-reanimated/assets/36106620/e855c796-a926-48bf-b55d-80014694043d"
/> | <video
src="https://github.com/software-mansion/react-native-reanimated/assets/36106620/004bd2f6-2bb7-41b2-af1d-6d98a94908c0"
/> |

Expected behavior:
- The component stays in the original position.
- Starts the fade-out animation.
- Wen component is invisible, changes position to the target position.
- Starts the fade-in animation.

In the previous approach, when the `delayFunction` was not specified
(when no one called `.delay()`), the component jumped to the final
position after 50ms instead of waiting until the component became
invisible.

## Test plan

I tested it on the example from
#6151
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants