feat(android-nav3): Android Nav3 integration - #6105
Closed
0xadam-brown wants to merge 5 commits into
Closed
0xadam-brown wants to merge 5 commits into
0xadam-brown wants to merge 5 commits into
Conversation
9 tasks
Contributor
|
This was referenced Sep 12, 2026
📲 Install BuildsAndroid
|
0xadam-brown
changed the title
Establish the new Android Navigation 3 integration module and register it with the build and publication metadata. This keeps the first step focused on the module boundary itself, without introducing generated API surface or implementation code yet. Co-Authored-By: OpenCode <noreply@opencode>
Introduce the route translation layer for Navigation 3 so later stages can reason about route names and sanitized arguments in one place. At this stage the module still exposes no meaningful public API surface.
Add the observer layer that turns Navigation 3 back stack changes into breadcrumbs, scope state, and navigation transactions. This is also the point where the module starts carrying generated BuildConfig version metadata and its first non-empty API snapshot.
Add the Compose-facing abstraction that binds Navigation 3 back stack changes to the observer layer. This establishes the integration’s primary API shape while keeping it internal until the rest of the sequence is ready to expose it.
Member
Author
|
Welp, my clanker just merged this whole PR stack save for the first when I asked it to make a change to one of the PRs. Sigh. I'll close and then try again... |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
PR Stack (Android Nav3)
📜 Description
This is the collection branch for the Android Nav3 stack.
It carries no feature code itself. The implementation is split across the stacked PRs below so the
module scaffold, route modeling, observer layer, and Compose-facing effect can be reviewed
independently and merged forward with merge commits before this collection branch is squash-merged
into
main.💡 Motivation and Context
Nav3 support is large enough that reviewing it as one PR would hide the architectural boundaries.
This collection branch gives us a stable top-level PR for the whole effort while the stack lands in
reviewable steps.
💚 How did you test it?
This branch is intentionally empty apart from the collection commit. Each stacked PR contains its
own verification details.
📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Merge the stack bottom-to-top, then squash-merge this collection branch into
main.#skip-changelog