feat: use response location sensor for table and map#313
Merged
regeter merged 1 commit intogooglemaps:mainfrom Apr 30, 2026
Merged
feat: use response location sensor for table and map#313regeter merged 1 commit intogooglemaps:mainfrom
regeter merged 1 commit intogooglemaps:mainfrom
Conversation
Contributor
|
🎉 This PR is included in version 1.35.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
The sensor accepted by the Fleet Engine server is more useful to show than the primary sensor on the device which is usually static as ROAD_SNAPPED. Also added "API" as the type for when the location data was updated by the server instead of an SDK update.