| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Sorry, something went wrong.
📲 Install BuildsAndroid
|
Sorry, something went wrong.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 061c4c3. Configure here.
Sorry, something went wrong.
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.
| * Doing so prevents route names from being obfuscated while leaving per-route arguments to | ||
| * [RouteArgumentsExtractor]. | ||
| */ | ||
| @ApiStatus.Experimental |
There was a problem hiding this comment.
Marked as experimental b/c this will be made public in a follow-on to the current PR stack. (Same below.)
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Stack (Android Nav3)
📜 Description
To support Nav3 we have to map a host app's back stack to an internal representation suitable for the Sentry data we emit. This PR introduces the core logic for doing so in the form of a RouteTranslator.
Note that the RouteResolvers passed to the translators constructor are defined by the host app, and so we're careful to protect against misuse / unintended performance issues.
💡 Motivation and Context
addresses: JAVA-274
💚 How did you test it?
📝 Checklist
🔮 Next steps
Build the observer layer that consumes these routes and updates Sentry state.
#skip-changelog