[v0.13.3] HistoryLocation no longer fires run callback

[ericclemmons]

First, I apologize if this issue is covered elsewhere, but my searching didn't turn up either a solution.

The issue was first discovered in ericclemmons/react-resolver#75 & ericclemmons/react-resolver#78.

Given:

export default (
  <Route handler={App}>
    // Query-able URLs (for POSTs & crawlers)
    <Route name="query.repo" path="/repo" handler={Stargazers} />

    // Canonical URLs
    <Route name="home" path="/" handler={Home} />
    <Route name="user" path="/:user" handler={Stargazer} />
    <Route name="repo" path="/:user/:repo" handler={Stargazers} />

    <NotFoundRoute name="404" handler={NotFound} />
  </Route>
);

and the usual:

Router.run(routes, Router.HistoryLocation, (Root) => {
  console.log("Routed!"); // This is here to confirm routing has taken place!
  Resolver.render(() => <Root />, document.getElementById("app"));
});

You can see routing stops working after the history changes the first time:

However, React Router v1.0.0-beta3 works as expected:

In my testing, HashLocation works correctly.

Is this a not-so-obvious error on my part, or something that will need a more time-intensive test-case to reason about? 😜

[ericclemmons]

After digging into the issue like crazy, the best I can assume is that context or something goes haywire.

That's the best I've got. Anyway, released React Resolver v2.0.5 with a fix that just neuters some functionality since it's a common edge-case:

https:/ericclemmons/react-resolver/blob/master/CHANGELOG.md#v205---2015-09-07