Toolkit UMD naming

[rjimenezda]

The UMD module names are a bit of a mess right now. They are long, verbose, and not namespaced.

We should try to come up with a relatively short way of naming packages, maybe even namespacing?

IDEA: We could have different entry points for the UMDs, so they build a namespace. We shouldn't use carto. because I think VL and carto.js will not play nice.

[VictorVelarde]

At this point in time, I think we should go for a new namespace, starting from 'carto' root.

Something in the line of:

• carto.vis: new viz classes to come
• carto.data (<-- sql): SQL API and more to come
• carto.auth: Auth / OAuth stuff
• carto.maps: Maps API
• carto.customStorrage (maybe just rename it to carto.kepler package?)

Opening the discussion with you @jesusbotella, @neokore and @elenatorro

[rjimenezda]

As long as it doesn't clash with VL and carto.js, which also live under 'carto'

[VictorVelarde]

or even if it does... 😄 (more to come soon...)

[neokore]

Taking carto as root is great, it makes easy to remember and sticks the library with the brand, but depending on how it will be distributed, we may need to add some "legacy users" checks.
E.g. in case of reusing a CARTO package (let's say carto.js) and any user just upgrade it, it will be useful to detect legacy library calls (maybe the initialize methods) and throw an exception to alert that this library is not backwards compatible.

[jesusbotella]

I think we should use carto namespace no matter what.
The library/module is not intended to work alongside CARTO-VL or CARTO.js, they have their own modules starting from carto namespace. So no need to be backwards compatible with our own libraries.

[VictorVelarde]

We'll make the move just after merging metrics-event PR #56 , starting a new base 'viz', isolated from the current -rc.013 line