Relative path in $state.go should be based on the path of the controller which defined $state instead of the current path

[bachue]

For example, in http://jsfiddle.net/Bachue/cQmT7/

When we click a or b for the first time, the state will change correctly, but if we click any of them again, exception will be raised.

Although I know ui-sref tag can resolve this problem, but sometimes we may have to do more things(e.g. ajax) so we still need to use method.

Thanks.

[dlukez]

As $state is a shared service, one might think that it's behaviour should be consistent across controllers. This function could be called from other non-state controllers, like a directive, or straight use of ngController.

When #636 goes in you could keep a copy of the $state that was active when the controller was instantiated and pass it in to $state.go()

[timkindberg]

Yeah unfortunately I'm not sure this is a feasible request, per @dlukez reasons.