Replies: 1 comment
-
|
Probably not going to happen for two reasons. First is that NavigationPath is opaque. Second is that once NavigationPath is exposed I'll have to leave it that way, even if Apple improves the mechanisms in the future. Destinations, checkpoints, send... all exist in order to leave views in the dark about where they are, how they got there, and how to return. I've been considering adding a few new logging conditions, but navigation is problematic when used initiated swipe gestures are used to pop and dismiss views. |
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
Uh oh!
There was an error while loading. Please reload this page.
-
Our app needs to report some even trapping, which have information related to the navigator stack, such as the current page and the previous page.
Currently, we get the navigator stack information by getting the NavigationPath and then parsing it, but the sheet and cover information cannot be obtained from the NavigationPath.
It would be very helpful if Navigator could log and access the navigator stack information in the framework.
Beta Was this translation helpful? Give feedback.
All reactions