CARTO v9 API tracker

[felixpalmer]

Tracker for work needed to land the new API for interacting with the CARTO backend.

Tasks

• RFC CARTO v9 API RFC #8051
• Initial implementation Carto: Initial implementation of v9 API #8130 against 8.9
• Test & review internally
• Fix binary data (to make vector layers work) Binary attribute support #8153
• Initial implementaion against master CARTO: Initial implementation of v9 API #8167
• Update website example CARTO: Update website example to use v9 API #8191
• Update playground example CARTO: update playground example to use new API #8192
• Update pydeck
• Remove CartoLayer CARTO: Remove CartoLayer #8217
• Cleanup maps-v3-api CARTO: Update fetchMap to use new APIs #8224
• fetchMapsupport CARTO: Update fetchMap to use new APIs #8224
• Error checking to catch runtime errors (for JS users who won't get TS hints)
• Documentation [docs] CARTO v9 docs #8228
• Fix tests

[aaranadev]

About the RFC #8051, I have a doubt about React considerations.

Now the access_token is required into new source functions, so the access_token need to add as dependency in useMemo, I would like to see how the workflow is affected if access_token changes or if you add it to the dependency array.

For instance:

• the access_token expires
• the access_token is changed by the user

As far as I know, Maps API instantiation needs to be renewed.

cc: @menusal @VictorVelarde

[felixpalmer]

Now the access_token is required into new source functions, so the access_token need to add as dependency in useMemo, I would like to see how the workflow is affected if access_token changes or if you add it to the dependency array.

In the case of a changing access token, it would be included in the useMemo dependency Array, which as you say will then trigger a new instantiation

[aaranadev]

Now the access_token is required into new source functions, so the access_token need to add as dependency in useMemo, I would like to see how the workflow is affected if access_token changes or if you add it to the dependency array.

In the case of a changing access token, it would be included in the useMemo dependency Array, which as you say will then trigger a new instantiation

Yes, perfect. I would like to test it when possible. Thx!

[felixpalmer]

@aaranadev we've come up with a pattern which avoids the need for using useMemo: #8214

[aaranadev]

@aaranadev we've come up with a pattern which avoids the need for using useMemo: #8214

Oh great! I see the REQUEST_CACHE map being replaced