Edge case where no activate function gets called after a redirect about abstract-state-router

[TehShrike]

Both the alpha and bravo states are implicitly at route / because they don't have any parents with a route, and they don't have any route, and empty strings are treated as /.

All state transitions are triggered by a url change, so when the alpha state loads (prompted by navigating to the / route) and tries to initiate a transfer to the bravo state, it attempts to change the url... to /. Which doesn't trigger any "route changed" events, because it was already at that route. (And if it did trigger a route changed event, it would just load alpha again, because that's the first state at that route).

If you give the bravo state a route, and then load #/, it redirects to #/bravo and loads the state correctly.

[ArtskydJ]

If this is a user-error, I can accept that. Ideally, if we can note it in a simple way in the readme, that might be nice.

Does this mean that it is unsupported to navigate to another state with the same route? Right now I get this error:

router.on('stateChangeCancelled', e => console.log(e.message)) // => "This probably shouldn't happen, open an issue or something"

Maybe I should get an error like:

router.on('stateChangeCancelled', e => console.log(e.message)) // => "Unable to navigate to a state with the same route"

[TehShrike]

I think the reason you got that error is because you were throwing inside of the event handlers for the state change cancel/error, not because of the duplicate routes.

I'm not sure what an appropriate warning would be in this case - maybe "you attempted to navigate to route / but you were already there"? Maybe the hash-brown-router could emit an error or something if there were multiple handlers found for a route?