The reason I chose to submit this is because it was initially unclear from the docs that the transition group needed to already be mounted in order for it to work properly.
Added docs for `React.isValidClass` and `React.isValidComponent`.
Still missing top level api:
* `constructAndRenderComponent`
* `constructAndRenderComponentById`
* `withContext`
When I first read these docs, it was not immediately clear to me that I could
use `React.addons.CSSTransitionGroup` to animate a single item coming into view,
or an item replacing an item already there. This was partly due to the example
which rendered a list of items.
This PR adds a blurb about being able to use
`React.addons.CSSTransitionGroup` with one or zero items, provides a code
example, and adds a note blockquote that a `key` attribute must always be
provided on each child of `React.addons.CSSTransitionGroup`. The latter point
was not immediately obvious from the original `TodoList` code example, since it
renders a list which would normally require `key` attributes anyway.
Test Plan:
- Refreshed `http://localhost:4000/react/docs/animation.html`, saw that the
docs additions rendered correctly.
- Example code not tested (it was extracted from working code).
Whilst this is intentional behaviour (see #1274), it is not documented anywhere, so it is worth mentioning.
It would also be nice if React issued a warning to console if a cloned component loses its key (as this will silently break reconciliation?)
This order should make more sense; it moves important functions like React.renderComponent up and deprecated/discouraged ones like transferPropsTo and setProps down. No content changes.
Julen Ruiz Aizpuru
fisherwebdev
Michael Randers-Pehrson
IvanVergiliev
Chris Sciolla
Dmitrii Abramov
Michael Chan
Charles Marsh
Paul O’Shannessy
Mike D Pilsbury
Andre Z Sanchez
Nathan White
Adam Mark
Sam Selikoff
Jan Hancic
Jan Hancic
Ben Alpert
Julien Bordellier
Jim OBrien
cutbko
Sébastien Lorber
David Hu
WickyNilliams
Cheng Lou
Tom Hauburger
Glen Mailer
Nick Williams