This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
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.
This PR adds a few missing header references to the macOS project and shares the runtime styling unit tests between the iOS and macOS test target. Despite the headers being missing from the project, the SDK still compiled without errors because the headers were already in the header search path. If they had been public headers, the compiler might’ve issued a warning about an incomplete umbrella header or non-module include statement. Unless we decide to go ahead with #5942, we’ll just have to remain vigilant about private headers that fly under the radar.
The runtime styling API can now round-trip colors without losing accuracy. Previously, we were using one color profile when converting NSColor to
mbgl::Color
and another when converting back to NSColor.On macOS, we have to set the access token to a bogus access token before running any tests. The macOS implementation of MGLMapView doesn’t even attempt to set a default style if the access token is missing, because in macosapp, the access token may be set asynchronously by the user when the preferences window appears.
I’m targeting this PR against the release-ios-v3.4.0 branch because I intend to issue a macOS SDK release that’s as close to iOS SDK v3.4.0 as possible, and I want to ensure as much test coverage as possible.
/cc @frederoni @incanus