Components are not passed static props about react-router HOT 7 CLOSED

+1 to a desire to pass props to the handler components.

I've checked a few of the examples, all of which sneak dependencies into the handler components via enclosed variables in getInitialState. Where'd you find documentation on passing props to them via the router?

from react-router.

Per #28, seems you just pass props to the Route, and it passes them on to its handler.

from react-router.

Props that are passed to the Route component that are not reserved for use by the router are passed along to the handler component. These are called "static" props because they are only declared once, when you first declare your routes.

@abrkn The API changed significantly in 0.2.0. Instead of using a Router you now just pass a Route directly to React.renderComponent. On the first pass, the handler's props are undefined. As soon as the route is mounted it runs all transition hooks needed to sync with the current URL. When this is done, it knows its props which include any static props that were passed to the Route.

Do you need to be able to pass static props through to the handler on the first render pass? If so, we could easily make that change.

from react-router.

Would that eliminate React's regular complaint on page load?

Warning: required prop activeRoute was not specified in App.

This is ~my fault; I added a propTypes entry for activeRoute in my top level route's handler to make sure I didn't screw up. I was surprised it was created for the first time without one.

from react-router.

No, it wouldn't. It's not ok to assume that activeRoute will always be there because the initial transition needs to happen when the page first loads.

For example, say you're visiting a page that requires auth, but the user isn't logged in. You'll probably have a willTransitionTo hook somewhere in the route hierarchy that does a transition.redirect('/login') as in the auth-flow example. So there's a short period of time when the page first loads where activeRoute is not defined because we're still running the initial transition.

from react-router.

@abrkn I believe this issue can be closed now. Can you confirm/deny?

from react-router.

This is a month old and appears to not be an issue anymore. Please re-open if I'm mistaken :)

from react-router.