bug: $ionicHistory should respect $state.go location: 'replace' option

[artlogic]

Type: bug

Platform: all

When moving from view to view using $state.go, it's possible to add a option to replace the current location with the location we're going to, rather that putting it on the history stack. For example:

$state.go('app.logout', null, {location: 'replace'});

Ideally, if this option is passed to $state.go, $ionicHistory should replace as well. As it stands today, it simply pushes the last address onto the stack.

[Ionitron]

Greetings @artlogic!

I've closed this issue because my sensors indicated it was old and inactive, and may have already been fixed in recent versions of Ionic. However, if you are still experiencing this issue, please feel free to reopen this issue by creating a new one, and include any examples and other necessary information, so that we can look into it further.

Thank you for allowing me to assist you.

[zenkalia]

this is still an issue 😿 👍 😿

[artlogic]

@zenkalia - I wasn't able to verify it was still an issue (I found an alternate solution) after the ticket was auto-closed. I'd love to see this get fixed. If you could submit a new issue (as suggested above), I would appreciate it. Maybe it'll get someone's attention this time around.

[zenkalia]

i might just do that if i haven't solved this tomorrow...

what alternative solution did you use? this one?:
#1287 (comment)

i'm using a side menu and am having trouble pulling in $ionicHistory to
use that hack. :\

On Mon, Dec 14, 2015 at 7:05 PM, James Kruth [email protected]
wrote:

@zenkalia https://github.com/zenkalia - I wasn't able to verify it was
still an issue (I found an alternate solution) after the ticket was
auto-closed. I'd love to see this get fixed. If you could submit a new
issue (as suggested above), I would appreciate it. Maybe it'll get
someone's attention this time around.

—
Reply to this email directly or view it on GitHub
#4109 (comment).

[artlogic]

In my particular case, I was able to get away with simply blowing away all history:

$ionicHistory.nextViewOptions({ historyRoot: true });

I'm surprised you aren't able to inject $ionicHistory. Is there a circular dependency problem?