updating to maplibre v10.0.2 #49
Merged
Conversation
This file contains 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
birkskyum
approved these changes
Feb 25, 2023
|
It would be great to add these changes to a changelog entry before merging |
|
Sure I will |
|
I mentioned changes in changelog file |
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.
✨ Features and improvements
-Updated maplibre version to v10.0.2.
-Incremented minSdk version from 15 to 21 to work same as maplibre implementation.
-Created custom classes for
GoogleLocationEngineImpl,Utils,LocationEngineProviderwhich were removed from default implementation maplibre to provide working with GSM location.-Corrected resource calls due to renamed res files in maplibre (from
mapbox_tomaplibre_).