fix(carto): RasterTileLayer fix to support external loadOptions #9561
Conversation
This file contains 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
zbigg
changed the title
donmccurdy
approved these changes
Apr 3, 2025
zbigg
force-pushed
the
zbigg/carto-raster-tile-loader-loadOptions-fix
branch
from
6407e25 to
113b507
Compare
zbigg
force-pushed
the
zbigg/carto-raster-tile-loader-loadOptions-fix
branch
from
113b507 to
8e14a34
Compare
felixpalmer
pushed a commit
that referenced
this pull request
Apr 14, 2025
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.
RasterTileLayer requires specific properties (metadata) passed to loader.
Passing custom
loadOptionsas props, overridesloadOptions.cartoRasterTile.metadataand layer loader always fail to parse tile.Change List