clearHistory doesn't work with router-outlet

[sebawita]

When navigating with clearHistory flag set to true with router-outlet, the history doesn't get cleared. So the flag has no effect at all.
Button text="login" [nsRouterLink]="['/main']" clearHistory="true"></Button>

The same applies when calling navigate through code:

navigateHome() {
    this.routerExtensions.navigate(['/home'], { clearHistory: true });
}

When I call the canGoBack() after navigating I always get true.
this.routerExtensions.canGoBack() => returns true;

[NickIliev]

Hey, @sebawita with the current implementation this is by design. It is expected that clearHistory would work with page-router-outlet (where we have page navigation) and not with router-outlet.
e.g.: If we have a router-outlet like this one here and I want to introduce clearHistory for one of the links then the expected behavior is not very clear.

[sebawita]

@NickIliev I am aware that this is done by design.
What happens when I use clearHistory in the scenario of a router-outlet being nested in a page-router-outlet? Would that clear the navigation history?
If yes, then this would look like we should be able to clear the navigation history of the "root" Outlet, regardless whether it is a page-router-outlet or router-outlet.

Maybe for router-outlet, we could require the router-outlet components to be named. Like:
<router-outlet name="dogoutlet"></router-outlet>
(See the full example at: https://github.com/sebawita/nativescript-nested-router/blob/master/app/dog-tab/dog-tab.component.html)
So that we could call clearHistory like clearHistory="['dogoutlet']"

As it is, navigating in router-outlet causes the navigation stack to grow with no way clear it, but with routerExtension able to operate on it. This is somewhat confusing.

[Pinny3]

So, what's the status here? How can I clear history using a router-outlet?

[alexma01]

Solved?