Replies: 2 comments
-
This seems like a user-specific use-case, so couldn't this be implemented in userland instead of Core? (If the properties are private, then fair enough, but I don't think holding onto an arbitrary history stack is a good idea in terms of memory management). |
Beta Was this translation helpful? Give feedback.
0 replies
-
I agree with you but it is a lot off stuff to do that each time we call navigate! I am using Core and if we haven't implemented a router we couldn't handle it. I think it is a good think if NS propose a variety of helpers, I see that positive :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi @NathanWalker
It will be useful to keep the 10 last
Frame.navigationStackEntry: NavigationEntry[]
exposed to us, this can be handy for duplicated navigation scenario such as navigation when receive a notification, if we havenavigationStackEntry
then it is simple to check if we are in the same page.Each time we call
Frame.navigate()
we push the entry on the navigationStackEntry.Beta Was this translation helpful? Give feedback.
All reactions