-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HMS integration #9
base: main
Are you sure you want to change the base?
Conversation
Separate CoLocation into two implementations: 1. `CoLocationGms` - GMS implementation 2. `CoLocationHms` - HMS implementation Let the `CoLocation.from` decide which `locationServicesSource` to use: when both GMS and HMS are available then use the GMS. Create `LocationRequest` and `LocationSettingsRequest` which are wrappers to the platform related classes and use them to define requests without using specific (GMS/HMS) classes. Change the minSdkVersion to 19 (HMS requirement). Create separate tests for both tools.
Add HMS integration
Add ability to switch between location providers.
Modify Sample app to be able to test HMS on Huawei devices
@@ -47,6 +49,8 @@ dependencies { | |||
implementation "androidx.lifecycle:lifecycle-runtime-ktx:2.3.1" | |||
implementation "androidx.lifecycle:lifecycle-extensions:2.2.0" | |||
|
|||
implementation "androidx.multidex:multidex:2.0.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huawei lib is too huge
Thanks for the contribution, it's really appreciated. Without looking too much into details of the PR, if HMS integration should be added, it should not be in the main library, but as a second library which depends on the main library, as an add on. Otherwise this would introduce HMS dependency even when users of the library only need to use Google services - which is probably still the most common way of using this library. If this is reworked in a way so that the HMS implementation is moved to a |
Update dependencies versions
Separate CoLocation into two implementations:
CoLocationGms
- GMS implementationCoLocationHms
- HMS implementationLet the
CoLocation.from
decide whichlocationServicesSource
to use:when both GMS and HMS are available then use the GMS.
Create
LocationRequest
andLocationSettingsRequest
which are wrappersto the platform related classes and use them to define requests without
using specific (GMS/HMS) classes.
Change the minSdkVersion to 19 (HMS requirement).
Create separate tests for both tools.
Modify Sample app to be able to test HMS on Huawei devices