Carto: Initial implementation of v9 API #8130
Closed
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
felixpalmer
force-pushed
the
felix/carto-v9-api
branch
from
4b4bef4
to
ad84218
Compare
|
@padawannn @zbigg @VictorVelarde can you help me with the review of this PR?. I'm not going to be able to check until the end of the week and don't want to slow it down |
felixpalmer
changed the title
aaranadev
reviewed
Oct 3, 2023
aaranadev
reviewed
Oct 3, 2023
aaranadev
reviewed
Oct 3, 2023
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.
For #8047
Background
READ FIRST: Implements RFC detailed here
Based off 8.9 to ease testing. This PR will not be merged into master until binary data handling is fixed in the
VectorTileLayerChange List
_CartoTileLayer->VectorTileLayer& export previously private Layers