Update framer-motion to v11.0.6 from v6.3.3 fixing post state update on feed type change #5
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
…on feed type change
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
This pull request focuses on updating the framer-motion library from version
6.3.3to11.0.6. The primary motivation for this update was to resolve an issue with the<AnimatedPresence>component. Previously, even after updating the posts array, the component caused old posts to remain displayed but hidden, occupying space with an opacity of0. This behaviour was due to a bug in the library itself. By upgrading to version11.0.6, we address this issue directly, ensuring that the post state is properly updated when changing the feed type, and posts display as expected without lingering hidden elements.