Repository navigation
Release 1.3.2 - #13
Merged
Merged
Conversation
bearing を「値を増やすと地図が時計回りに回る」向きに統一し、ネイティブ SDK との変換をコアの CameraBearing に集約する。
moveCameraTo(cameraPosition:) ran every camera through resolveCameraPosition, which read `zoom == 0 && bearing == 0 && tilt == 0` as "the caller only gave me a position" and replaced the requested camera with the stored one, keeping the position alone. A camera that really does ask for zoom 0 — the whole world — matches that test exactly, so it was the one camera the map would not move to. It shows up as a feature that does nothing rather than as a wrong value: the map stays where it was, so what that invites you to conclude is that zoom 0 is unsupported. Position-only already has a way to be said: the `moveCameraTo(position:)` overload. Inferring the same intent a second time from the *value* costs a legal zoom, and cannot tell `MapCameraPosition(position:)` from one written with `zoom: 0` anyway — zoom defaults to 0, so by the time a camera arrives the two are one value. android-sdk never had this; MapViewState.kt hands the camera straight to the controller. js-sdk-core carried the same code and loses it in the same change (MapConductor/js-sdk-core#4), so all three platforms now agree.
…n under the tap (#12)
This was referenced Oct 23, 2026
wf9a5m75
added a commit
that referenced
this pull request
Oct 24, 2026
Release 1.3.2 (#13) bumped MapConductorCore.podspec on main only, so develop still said 1.3.1. This is the only difference between main and develop.
wf9a5m75
added a commit
that referenced
this pull request
Oct 24, 2026
* Make bearing a clockwise map rotation (#10) bearing を「値を増やすと地図が時計回りに回る」向きに統一し、ネイティブ SDK との変換をコアの CameraBearing に集約する。 * fix: zoom 0 is a zoom, not a missing one (#11) moveCameraTo(cameraPosition:) ran every camera through resolveCameraPosition, which read `zoom == 0 && bearing == 0 && tilt == 0` as "the caller only gave me a position" and replaced the requested camera with the stored one, keeping the position alone. A camera that really does ask for zoom 0 — the whole world — matches that test exactly, so it was the one camera the map would not move to. It shows up as a feature that does nothing rather than as a wrong value: the map stays where it was, so what that invites you to conclude is that zoom 0 is unsupported. Position-only already has a way to be said: the `moveCameraTo(position:)` overload. Inferring the same intent a second time from the *value* costs a legal zoom, and cannot tell `MapCameraPosition(position:)` from one written with `zoom: 0` anyway — zoom defaults to 0, so by the time a camera arrives the two are one value. android-sdk never had this; MapViewState.kt hands the camera straight to the controller. js-sdk-core carried the same code and loses it in the same change (MapConductor/js-sdk-core#4), so all three platforms now agree. * Add labelPosition to the default marker icon and pick the marker drawn under the tap (#12) * Release 1.3.2
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
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.
Every provider on develop already declares
from: "1.3.1", but none of them compile against the 1.3.1 tag. They use core API that landed after it:CameraBearing(Make bearing a clockwise map rotation #10, clockwise bearing)MarkerHitTest.pick(Add labelPosition to the default marker icon and pick the marker drawn under the tap #12, labelPosition / tap selection)Resolving the providers through the remote URL fails with
cannot find 'CameraBearing' in scopeandtype 'MarkerHitTest' has no member 'pick'. This releases develop as 1.3.2 so the providers can raise their minimum to it.This PR only bumps
MapConductorCore.podspecto 1.3.2 on top of develop (main is an ancestor of develop, so nothing on main is lost). 240 unit tests pass on the iOS Simulator, and the sample app builds with every provider against this core.After merge: tag
1.3.2on main, then raise each ios-for-* tofrom: "1.3.2".