-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Conversation
To be discussed:Change packages when we deprecate MapView in future releaseThis change is required to hide private API with package visibility, Let me explain this with Google's implementation:
Above system doesn't match with our current package system because MapView is located in
Possible solutions:
|
While doing winter cleaning I have identified some API that needs to be deprecated: I'm removing these methods from |
How does this relate to the branch / PR #3485 ? Should that one be closed now? |
@bleege |
@tobrun Cool. Thanks for clarifying. There's always so many tickets flying around it can be hard to keep track of which are the germane ones. |
There is some confusion about this. As mentioned and explained here also, the Mapbox API will be mirroring the use of the Google Maps API. This means that Mapbox will have a |
Good catch! FWIW, I'm fine with |
@bleege
But I will now focus on getting parity with GoogleMap, without the compatibility support. |
@tobrun No problem at all! Always happy to clarify on things. I remember @zugaldia mentioning that too, but I thought we dismissed it as we were going to do a full |
@bleege @tobrun Indeed 3.1.0 is shaping up really nice with 47 closed tickets as of now: https://github.com/mapbox/mapbox-gl-native/issues?q=is%3Aissue+milestone%3Aandroid-v3.1.0+is%3Aclosed |
52cb25b
to
7080ce9
Compare
A lot has happened in this branch, now that we have a 3.2.0 release branch and an release date. |
This is the list of items that I want to resolve before merging
These are the items that not made the list:
|
fc1f18f
to
b635fbc
Compare
CI Approved going to rebase and merge |
b635fbc
to
8ed1dc9
Compare
closes #3145.
As discussed with @bleege and @zugaldia, the introduction of
MapboxMap
must be completely backwards compatible in next release.This has resulted in following decisions:
getMapAsync()