Cursorily copy-edited the data-driven styling guide, removing a stray class reference, replacing a redundant h1, and making stops examples platform-agnostic and less redundant.
Fixed an issue in the style authors guide where style function tables appeared under each style layer type table.
* [android] execute resource transform callback on the right thread
* [android] allow resetting of resource transform callback
* update CHANGELOG for v5.0.2
* [android] - correct anchoring when Icon is updated (#8519)
* Revert "[android] - only dispatch events if not handled by MarkerView (#8447)"
This reverts commit 09d76854ab.
* Revert "[android] - move touch handling of MarkerViews back to View#setOnClickListener. Workaround panning issue by dispatching touch events to the parent ViewGroup. (#8272)"
This reverts commit 1693b389d7.
`- (nullable UIView <MGLCalloutView> *)mapView:(MGLMapView *)mapView
calloutViewForAnnotation:(id <MGLAnnotation>)annotation;` bridges
with a `UIView?` return type in Swift. This changes replaces the
`UIView` type in the method signature so that, when bridged to Swift,
the returned object is defined as `MGLCalloutView?`.
* [android] [auto] Update properties to version 5.0.0 in preparation for build.
* [android] - bump snapshot version
* [android] remove typo in gradle-javadoc.gradle
* [android] revert to 5.0.0-SNAPSHOT
* [android] revert to 5.0.0
* [android] [auto] Update properties to version 5.0.0 in preparation for build.
* next release is now 5.1.0-SNAPSHOT
- Changed `make style-code-darwin` to `make darwin-style-code` in relevant files
- Added some doc clarifications:
- `MGLInterpolationModeExponential` and `MGLInterpolationModeInterval` can be used with `MGLCameraStyleFunction` (I am not sure how to accurately reflect this in the documentation for `MGLCompositeStyleFunction`)
- Do not add a style layer to the style property on a map view before the style has finished loading
- Create individual style layers from a `MGLShapeCollectionFeature`
Resolved unused variable warnings in Release configuration that occurred because they were only used within NSAssert() invocations, which are omitted from Release builds.
