react-motion
Advanced tools
Changelog
0.2.0 (July 22th 2015)
willLeave
returning false
will now keep the key. Only null
and undefined
will serve as a signal to kill the disappeared key.willLeave
previously failed to expose the second argument correspondingValueOfKeyThatJustLeft
. It's now exposed correctly.willLeave
is now called only once per disappearing key. It was called more than once previously as a implementation detail. Though you should never have put side-effects in willLeave
. It's still discouraged now.this.props.handlerThatSetStateAndUnmountsSpringInOwnerRender()
in Spring
's endValue
, Spring's already scheduled requestAnimationFrame
will no longer cause an extra setState
since it's unmounted. But in general, please don't put side-effect in endValue
.requestAnimationFrame
). #57requestAnimationFrame
polyfill.Changelog
0.1.0 (July 14th 2015)
TransitionSpring
's willEnter
's callback signature is now (keyThatEnters, correspondingValue, endValueYouJustSpecified, currentInterpolatedValue, currentSpeed)
(added correspondingValue
as the second argument). Same for willLeave
.Spring
is now no longer exposed as a default, but simply as "Spring": require('react-motion').Spring
. Or import {Spring} from 'react-motion'
.Spring
and TransitionSpring
's children
function now expect a ReactElement. The components will no longer wrap the return value in a div
for you. #44 #20endValue
without {val: ...}
wrapper.