State name should be optional to `state.go` about abstract-state-router HOT 4 CLOSED

I've created 3 failing tests for this in my branch

The last one, 'calling redirect with no stateName in resolve should use current state', has an issue where the 'second' state never gets called.

from abstract-state-router.

The tests should be good now (I added route strings). I pushed them up to https://github.com/TehShrike/abstract-state-router/tree/83-null-state-name-passed-to-go-function

from abstract-state-router.

I think that the "current state" should be the one that you're transitioning to. That way if you pass in null to the redirect function inside a resolve, you will be going to that same state instead of the state before.

This behavior is asserted by the third test @daytonlowell wrote, so as soon as those new tests are passing and the docs are updated then the feature should be good to go.

from abstract-state-router.

Published as 5.13.0

from abstract-state-router.