Repository navigation
feat(nav3): [Part 8] Define bounded property encoding - #6705
Draft
0xadam-brown wants to merge 2 commits into
Draft
0xadam-brown wants to merge 2 commits into
0xadam-brown wants to merge 2 commits into
Conversation
This was referenced Nov 20, 2026
Contributor
|
5 of 9 tasks
Contributor
PR risk: mediumFor commit Main concerns: public contract, data sent to Sentry, reach. Rules that block low also fired:
This label is a hint for reviewers, not an approval. |
This was referenced Nov 20, 2026
📲 Install BuildsAndroid
|
4 of 9 tasks
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
Route properties can now be encoded as navigation arguments subject to size and structural limits, with sensitive-key filtering applied to nested data. This policy is introduced before the properties mapper becomes public.
Values under keys matching Sentry's sensitive denylist are filtered, including within nested data. That is a limited safeguard for common secrets, not a general PII filter: applications must still decide which route properties are appropriate to send. The public mapper introduced next makes that choice explicit.
💡 Motivation and Context
Automatically turning route properties into navigation arguments needs a consistent policy for nested data, payload limits, and fields that contain secrets. The built-in path should follow the same structural rules as custom mapper output.
addresses: JAVA-787 (link)
💚 How did you test it?
Nav3 release build and all 752 unit tests passed. Repository-wide
make format api, Spotless checks, ABI validation, and Detekt passed. The 10 affectedHttpUtilstests also passed.📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Continue with PR 9: Add SerialNameAndProperties.
#skip-changelog