Introduce top-level Navigator
as the entry point for all navigation
#41
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.
Previously in
turbo-android
, the library was structured like:This makes substantial changes to make the library more inline with the iOS library. Instead of navigation APIs existing in multiple places, such as the
*ActivityDelegate
and the*Destination
interfaces, all navigation flows through a singleNavigator
API. The structure looks like:This reduces the need to ever interact directly with a
NavHostFragment
or aSession
. TheNavigator
(available in theHotwireActivity
and every destination screen) provides all the navigation APIs an app needs: