Xamarin Forms Routing #724
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We have to do this or else we won’t create a new AppState
Scheduling this makes setting things up in your app’s OnCreate way harder
This brings the scheduler in-line with the iOS scheduler (and also solves some OnCreate ordering issues)
Also, handle common mistakes like not registering views properly. We still have to look up a Screen from the Locator though which kinds of defeats the purpose of the router, because if you don’t present a view immediately on construction, NavigationPage crashes
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR enables Routing for Xamarin.Forms apps, along with fixing some bugs along the way to make the routing and app suspension scenarios work.