You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we want to navigate backwards, removing pages from the stack, it is not possible to do it if it is not done with the Frame.
An example of doing it manually is the following:
constframe=Frame.topmost()constbackStack=frame.backStackconstentry=backStack[0]// your destination hereframe.goBack(entry);
The problem with doing it manually and not through ns-vue is that custom routers lose navigation history
The text was updated successfully, but these errors were encountered:
The problem with doing it manually and not through ns-vue is that custom routers lose navigation history
That shouldn't matter if the custom router relies on the frame/page events to keep track of it's internal history. If the router implements it's separate history - that's going to be an issue in various cases where it can get desync'd from the actual state.
But regardless, this is useful to implement on the $navigateBack apis 👍
When we want to navigate backwards, removing pages from the stack, it is not possible to do it if it is not done with the Frame.
An example of doing it manually is the following:
The problem with doing it manually and not through ns-vue is that custom routers lose navigation history
The text was updated successfully, but these errors were encountered: