Should be pretty easy -- most of the work will be in identifying areas of shared code, making it more "multi-provider," etc. Although in v1 I recall it was necessary to add a fields collection to fetch human-readable versions of field names. That doesn't apply to carto, so thinking through how/whether to accommodate that will be a thing.
Should be pretty easy -- most of the work will be in identifying areas of shared code, making it more "multi-provider," etc. Although in
v1I recall it was necessary to add afieldscollection to fetch human-readable versions of field names. That doesn't apply to carto, so thinking through how/whether to accommodate that will be a thing.