Is your feature request related to a problem? Please describe.
We would like to use Cube schema as the single source of truth for our SaaS data model, and need to add some data related to how each metric should be described / displayed on the front end.
For example, should it be displayed with a specific prefix or suffix (e.g. € or %), how many digits should be displayed, what is the description for each metric ...
Describe the solution you'd like
Two evolutions to data model and API v1/meta would be needed:
Data models should allow custom fields (in our case for example prefix / suffix / precision / description ...)
API v1/meta should expose those fields so that we can handle them on the SaaS side
Describe alternatives you've considered
Currently our solution is to include a stringified json "description" field in the Cube data models (other names are not accepted), and have our SaaS connect to our Github repo to get the code and parse it, which is fare from optimal
Is your feature request related to a problem? Please describe.
We would like to use Cube schema as the single source of truth for our SaaS data model, and need to add some data related to how each metric should be described / displayed on the front end. For example, should it be displayed with a specific prefix or suffix (e.g. € or %), how many digits should be displayed, what is the description for each metric ...
Describe the solution you'd like
Two evolutions to data model and API v1/meta would be needed:
Describe alternatives you've considered
Currently our solution is to include a stringified json "description" field in the Cube data models (other names are not accepted), and have our SaaS connect to our Github repo to get the code and parse it, which is fare from optimal
Thanks in advance for your help !