Repository navigation
ref(nav3): [Part 1] Repackage navigation internals - #6697
Open
0xadam-brown wants to merge 1 commit into
Open
0xadam-brown wants to merge 1 commit into
0xadam-brown wants to merge 1 commit into
Conversation
This was referenced Nov 20, 2026
Contributor
PR risk: mediumFor commit The model rated this change low. It was raised to medium because:
This label is a hint for reviewers, not an approval. |
This was referenced Nov 20, 2026
📲 Install BuildsAndroid
|
This was referenced Nov 20, 2026
0xadam-brown
marked this pull request as ready for review
November 20, 2026 14:17
0xadam-brown
requested review from
markushi and
runningcode
and removed request for
a team
November 20, 2026 14:17
This branch has not been deployed
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
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 (Nav3 Serial Name Mappers)
📜 Description
PR moves our non-public nav3 code into a new
.internalpackage, and introduces an.internal.backstackpackage as a sibling to.internal.lifecycle.Doing so makes it obvious what the public APIs are (SentryNavEffect, SentryNavOptions, and BackStackEntryMapper), and it lets us introduce another
.internal.backstack.kotlinxsubpackage later in this PR stack to sequester code that calls kotlinx.serialization APIs.This is a pure refactor / no behavioral or ABI changes.
💡 Motivation and Context
The Nav3 integration's public entry points previously shared a package with the machinery that tracks back stacks and activity ownership. As the integration grows, that arrangement makes it harder to distinguish the supported SDK surface from the state management behind it.
addresses: JAVA-787 (link)
💚 How did you test it?
n/a
📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Continue with PR 2: Extract shared back stack policies.
#skip-changelog