feat: expose createTheme as createCartoTheme

[AdriSolid]

Expose cartoTheme as createCartoTheme.

Related with documentation: CartoDB/documentation#78

[coveralls]

Pull Request Test Coverage Report for Build 729750896

• 0 of 1 (0.0%) changed or added relevant line in 1 file are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.2%) to 79.336%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
packages/react-ui/src/theme/carto-theme.js	0	1	0.0%

Files with Coverage Reduction	New Missed Lines	%
packages/react-ui/src/theme/carto-theme.js	1	72.73%

Totals
Change from base Build 680506927:	0.2%
Covered Lines:	547
Relevant Lines:	655

---

💛 - Coveralls

[VictorVelarde]

Are we sure we can remove default options?

[AdriSolid]

As described in documentation PR, the way to overwrite cartoThemeOptions is equal for both implementations in this way.

Also, passing to createTheme and object like:

const mainColor = { palette: { primary: { main: '#80000' }}}

results in an error. Do you have any other idea to handle this?

[VictorVelarde]

What if we leave the optional param, and just expose the method?

That way we could also allow overriding certain properties, so we would eventually get 3 options for the user:

• call to createTheme without params (one line from the client)
• call to createTheme with certain options (maybe just colors)
• completely custom case, using just cartoThemeOptions (what is currently being used from template)

/cc @borja-munoz

[VictorVelarde]

Please add a note to changelog and link here the PR with the doc change

[VictorVelarde]

We should talk more about this one with @borja-munoz, before exposing it

[VictorVelarde]

Not a clear advantage on the change, so I'm closing this