Proposal: new /sources folder about carto-react-template

[VictorVelarde]

Hi @Clebal!

I like the idea of a /data/sources. Just to have a clear idea of the other folder what contents do you propose for /data/models? can you put also an example?

Regarding to source file contents:

• 👍🏻 like having the ID, the SOURCE_COLUMNS and the SOURCE itself
• ❓ I have doubts about including the WIDGETS inside: if the idea is to split backend from front, shouldn't those widget properties be outside, as they are more related to the visual/frontend part? what do you think?

[juandjara]

I'm following this same structure in the site planning product project and in there, data/sources contains functions that return strings (sql strings for sources) while data/models contains functions that call the SQL API directly with executeQuery and return or process those results

[aaranadev]

@VictorVelarde , KPI_SOURCE_WIDGETS is the interface for the frontend, we don't want to know the column name and the operation about that column. We prefer a key and backend includes the operation and name column like they want

[VictorVelarde]

Ok, if it works for you and it fits the workflow, I'm ok with the SOURCE_WIDGETS side.

@albertoarana do you aggree on keeping the division between data/sources (declarative, for layers & widgets), from data/models (for custom queries against any api?)

[aaranadev]

I agree, maybe that X_WIDGETS won't be the best suffix. I would try with other name.

Any suggestion?

[aaranadev]

We will go to remove _WIDGETS from source finally

[VictorVelarde]

Already done