Issues with navigating across "top level" routes in contextual router

[gurdasnijor]

This issue can be repro'd as follows:

Create the 'top level router' component :

<Locations path={this.props.path} >
    <Location path="/test/*" handler={testContextRouter} />
    <Location path="/testothercontext/*" handler={testOtherContextRouter} />
</Locations>

'testContextRouter'

 <Locations contextual>
      <Location path="/" handler={function(props) { return React.DOM.div(null, 'test/ROOT') }} />
      <Location path="/:slug" handler={function(props) { return React.DOM.div(null, 'test/' + props.slug) }} />
</Locations>

'testOtherContextRouter'

 <Locations contextual>
      <Location path="/" handler={function(props) { return React.DOM.div(null, 'testothercontext/ROOT') }} />
      <Location path="/:slug" handler={function(props) { return React.DOM.div(null, 'testothercontext/' + props.slug) }} />
</Locations>

Now when navigating from, say /test/etc to /testothercontext/etc2 you'll find that the url seems to update without actually activating any handlers (after the initial route transition between them works)

Edit: Thinking through it some more; the navigation from /test/etc to /testothercontext/etc2 is being done by Link components rendered at the same level as the 'top level' router. Can the issue have something to do with that?

[andreypopp]

I've published 0.10.1, and now your case works for me. Can you confirm?

The bug was with incorrect unregistration of routers from environment — at some point non of the routers were registered at the environment and so no changes were propagated to them.

[gurdasnijor]

That fixed it; I was just about to submit a PR to update the Environment.unregister() after I tracked it down, but you're too fast! Thanks again!