Repository navigation
Fix Mapbox after Longdo in camera-sync demo - #46
Merged
Merged
Conversation
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.
The camera-sync example initially loads Longdo's external MapLibre, whose built-in constructor registrations break Mapbox tile serialization after switching providers. Isolate Mapbox's private registry key as well as the npm MapLibre key in the demo's development and production builds, allowing Longdo and Mapbox to coexist without changing the published SDK packages or external scripts.
Validation: four registry regression tests passed, including unmodified external MapLibre in both load orders; full basic-example build passed; local Longdo → Mapbox switching and camera movement verified. Lint passed with the existing HERE declaration warning.