feat: enhance navigation updates and lane information handling #525
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.
Updated NavForwardingManager to include NavigationUpdatesOptions
for improved navigation updates.
Enhanced ObjectTranslationUtil to extract and map lane information
from StepInfo, including lane directions and recommendations.
Refactored multiple method signatures in iOS modules
for consistency and clarity.
This PR enhances the
onTurnByTurnevent payload by adding optional lane guidancedata (
lanes) so developers can build fully custom turn-by-turn guidance UI(e.g. a lane row showing which lanes are recommended) instead of relying solely
on the default Google UI.
Example
lanespayload (when available):[ { "laneDirections": [ { "recommended": true, "laneShape": 4 } ] }, { "laneDirections": [ { "recommended": false, "laneShape": 1 } ] }, { "laneDirections": [ { "recommended": false, "laneShape": 1 } ] } ]Notes:
lanesis not always present. The Navigation SDK only provides lane guidancefor certain maneuvers/segments, so consumers should treat it as optional.
onTurnByTurnevent and does not remove orchange existing fields.
Pre-launch Checklist