Here's a rough draft proposal for an extension to the
animated component that can handle both simple and advanced FLIP use cases.
Initiate a FLIP animation on a component by updating the
Match unconnected components across renders by making sure they share the same
flipId prop, and when one unmounts and the other mounts, they will be connected with a FLIP animation.
Occasionally, like in the example below, users will want to be able to FLIP pre-existing springs, if for instance a FLIP could be interrupted by a drag.
The api allows for this as well, by passing in a
flipSet prop in addition to a
This is a first draft of the code wrapping the
animated component to make the above three use cases possible.
AnimationHandler outer wrapper attempts to simplify the most common use cases. However, if you pass in the
flipSet prop you can bypass this
to get total control of the animation to facilitate interruptability and more complex effects.
- Think about improving or simplifying
- Figure out chained staggering of FLIP components and/or whether it is necessary (react-flip-toolkit supports it).
- Figure out how to lazily import FLIP functionality into
animatedso as not to bloat the bundle for users who don't need FLIP. (or perhaps just have a
FlippableAnimatedcomponent or similar?)
- Make the springs customizable for abstracted FLIP cases (like examples one and two). this would be easy with a
flipSpringprop or something but that might start making the api too complex.