@samitouri / QOS-React-2 / commits / 76496b3cca

Add note about higher/lower-level transition APIs

Ben Alpert committed Jul 14, 2014 at 21:40 UTC 76496b3cca508105816c0497c305dc41b5633be4
1 file changed +4
docs/docs/09.1-animation.md
+4
@@ -88,6 +88,10 @@ You'll notice that when you try to remove an item `ReactCSSTransitionGroup` keep
88
89 You can disable animating `enter` or `leave` animations if you want. For example, sometimes you may want an `enter` animation and no `leave` animation, but `ReactCSSTransitionGroup` waits for an animation to complete before removing your DOM node. You can add `transitionEnter={false}` or `transitionLeave={false}` props to `ReactCSSTransitionGroup` to disable these animations.
90
91 +> Note:
92 +>
93 +> When using `ReactCSSTransitionGroup`, there's no way for your components to be notified when a transition has ended or to perform any more complex logic around animation. If you want more fine-grained control, you can use the lower-level `ReactTransitionGroup` API which provides the hooks you need to do custom transitions.
94 +
95 ## Low-level API: `ReactTransitionGroup`
96
97 `ReactTransitionGroup` is the basis for animations. When children are declaratively added or removed from it (as in the example above) special lifecycle hooks are called on them.