NavManager suppressLocationChanged option #25782
Closed
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.
Summary of the changes
LocationChanged
event when navigating withNavigationManager
.Addresses #25767.
This is just an example implementation. The real thing would wait on the results from #25752 to use a new
NavigationOptions
object if that's the result.Could using this option cause unexpected behavior? Perhaps... but it's completely opt-in. Someone using this would know what particular problem they're trying to solve. I hope the possibility of side-effects doesn't stop this being a viable option, as applying workarounds to get to this outcome are all sub-optimal.
(Note: I know there are tests failing, but since this is an example PR that is waiting for #25752, I'm not going to cloud up the file changes with fixing test objects that will need to be re-worked when the real PR comes about later.)