Fills NavigationResult Exception for Navigations where CanNavigate is false #1919
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
This makes
NavigationService.Push
return aNavigationResult
with aNavigationException
when the navigation is cancelled viaIConfirmNavigation
/IConfirmNavigationAsync
'sCanNavigate
method.Bugs Fixed
API Changes
None
Behavioral Changes
If a ViewModel tries to navigate and
CanNavigate
returns false, it will now return aNavigationResult
with aNavigationException
andSuccess = false
. This makesPush
consistent with the same behavior inBack
andBackToRoot
.PR Checklist