stateError and stateChangeError events should be combined about abstract-state-router HOT 3 OPEN

Yeah, it's really confusing what the difference between them is, and worse, I don't think the tests do a good job of asserting that they do the things specific to them (why is it a stateError and not a stateChangeError to navigate to a nonexistent state?).

A couple things:

1. is there any real distinction to be found?
   1. Is it notable that some error events only happen between state changes starting and ending? I think that might be the current logic. Maybe this could be indicated by just a boolean between state changes.
   2. how significant is the difference between an error happening in a user-land function (like the provided activate function, or event handlers) and some other error happening (not able to turn a state name into a route when go is called or not being able to find a matching state when evaluateCurrentRoute is called)
2. are any of these state routing issues serious enough to emit actual error events?

from abstract-state-router.

current stateError events:

Same for

For

Maybe that should just throw straight out as well? It seems like a different kind of "not found" than the traditional one I'd imagine existing, which would be "there was no matching route for the url in the location bar".

from abstract-state-router.

I would expect to be directed to the hashBrownRouter.setDefault (404) state if the state doesn't exist.

If there wasn't a hash, I would expect to go to the fallbackState.

If I call state.go('this.route.does.not.exist'), I would expect to have an error thrown.

from abstract-state-router.