Skip to content

Commit f66c528

Browse files
committed
Copy changes as per request
1 parent 277acd5 commit f66c528

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

docs/guides/overview.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -352,14 +352,15 @@ Important Note About Dynamic Segments
352352
If you have dynamic segments in your URL, a transition from `/users/123`
353353
to `/users/456` does not call `getInitialState`, `componentWillMount`, `componentWillUnmount` or `componentDidMount`. If you are using those lifecycle hooks to fetch
354354
data and set state, you will also need to implement
355-
`componentWillReceiveProps` on your handler, and its child components, just like any other
355+
`componentWillReceiveProps` on your handler and its stateful children, just like any other
356356
component whose props are changing. This way you can leverage the
357357
performance of the React DOM diff algorithm. Look at the `Contact`
358358
handler [in the `master-detail` example](https://github.com/rackt/react-router/blob/master/examples/master-detail/app.js).
359359

360-
If you would rather mount components normally when transitioning between dynamic segments, you can assign a unique key to your route handler component to bypass this optimization:
360+
If you would rather force route handlers to re-mount when transitioning between dynamic segments, you can assign a unique key to your route handler component to bypass this optimization:
361361

362362
```js
363+
// assuming App is top-level route
363364
var App = React.createClass({
364365

365366
mixins: [Router.State],

0 commit comments

Comments
 (0)