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
In Prism Forms we had the extension method GetNavigationUriPath, which when called would give you the current Uri of the INavigationService. In maui this extension no longer exists and reading the current Uri from a Viewmodel is incredibly difficult. We can observe the current Uri using the global navigation observer, however performing viewmodel based logic on the current Uri path is difficult.
API Changes
Add a new INavigationServiceExtension method named GetNavigationUriPath
Intended Use Case
Performing logic in a view model based on the page uri stack. For example we could have a Login page which can be accessed in multiple ways:
Open app for the first time, see a welcome flow & agree to privacy policy, complete flow and show login page. For this scneario we want to show a back button to go back into the privacy flow
Open app after agreeing to privacy, go directly to the login page. In this case we don't want to show a back button because we are at the bottom of our navigation stack.
The text was updated successfully, but these errors were encountered:
Hello @Axemasta I am also facing this issue when I am migration Xamarin.Forms application to MAUI. Please let me know if you have any workaround to get NavigationStack in MAUI then please share. will be really appreciated. Thanks.
Summary
In Prism Forms we had the extension method
GetNavigationUriPath
, which when called would give you the current Uri of theINavigationService
. In maui this extension no longer exists and reading the current Uri from a Viewmodel is incredibly difficult. We can observe the current Uri using the global navigation observer, however performing viewmodel based logic on the current Uri path is difficult.API Changes
Add a new
INavigationServiceExtension
method namedGetNavigationUriPath
Intended Use Case
Performing logic in a view model based on the page uri stack. For example we could have a Login page which can be accessed in multiple ways:
The text was updated successfully, but these errors were encountered: