feat(android-nav3): [Android Nav3 2] Model navigation routes - #6107
Draft
0xadam-brown wants to merge 1 commit into
Draft
feat(android-nav3): [Android Nav3 2] Model navigation routes#61070xadam-brown wants to merge 1 commit into
0xadam-brown wants to merge 1 commit into
Conversation
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.
This was referenced Sep 12, 2026
Contributor
|
📲 Install BuildsAndroid
|
0xadam-brown
added
the
deep-dive
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
Add the route modeling layer for Android Nav3.
This introduces the code that turns app-owned back stack entries into normalized route names and
sanitized argument payloads, along with focused tests for those translation rules.
💡 Motivation and Context
The rest of the Nav3 integration depends on having one place that defines what a route looks like
and which argument shapes are safe to propagate into Sentry state.
💚 How did you test it?
./gradlew :sentry-android-navigation3:testReleaseUnitTest./gradlew spotlessApply./gradlew apiDump📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Build the observer layer that consumes these routes and updates Sentry state.
#skip-changelog