Repository navigation
feat(nav3): [Part 10] Demonstrate the built-in mappers - #6707
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
|
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. |
5 of 9 tasks
4 of 9 tasks
📲 Install BuildsAndroid
|
0xadam-brown
force-pushed
the
feat/nav3-serial-name-mappers-10
branch
from
November 20, 2026 14:00
7a34760 to
f7b850a
Compare
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
The ordinary Nav3 examples should show the mapping approach that apps can use directly, so they now use serializable routes and the built-in mappers. This makes the examples demonstrate the same destination naming and property-collection choices offered by the SDK.
💡 Motivation and Context
The performance scenario needs to distinguish the cost of real built-in mapping from synthetic name and argument workloads. It therefore keeps the custom performance mapper and adds a choice to exercise the built-in mapper itself, so measurements can reflect the path an application would actually use.
addresses: JAVA-787 (link)
💚 How did you test it?
Nav3 release build and all 872 unit tests passed. Repository-wide
make format api, Spotless checks, ABI validation, and Detekt passed. The Android sample debug build passed after including its shared serialization-plugin setup in this slice.📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Continue with PR 11: Verify mapping after R8 minification.
#skip-changelog