Feature Ideas

It's possible to define metadata for cube model definitions. Cube suggests using this for "any information" for the frontend. See: https://cube.dev/docs/reference/data-model/cube#meta It would be perfect if we were able to define the preferred formatting, translations, and other information we might ever need for presentation purposes. This would eliminate the necessity to manually specify this information using Embeddable component editors. However -to my knowledge- the current iteration of the loadData() api does not provide any such metadata. It's the raw data only. This is especially useful for retaining consistency across multiple consumers, while minimising the amount of truth sources. E.g. background tasks for exports as well as presentation through our Embeddable components could both leverage this information to properly format currencies.

Wouldn't it be amazing if there was a copy/clone button close to the Edit and Delete ones 🥺

Rather than requiring clients to make a measure that contains math to generate a percent (eg: sql: 'ROUND(SAFE_DIVIDE({num1}, {num2}) * 100, 0)' and then using a posttext meta of '%') could we support Cube's format: percent setting to just send the data as a percentage automatically? This might also be useful for other formats Cube supports Example: name: example_percent title: Example Percent type: number sql: 'SAFE_DIVIDE({num1}, {num2})' format: percent description: an example using cube's format value

Drilldowns are super helpful for end users, so being able to add them within the no-code builder is really important - e.g. by opening a sub-embeddable via a modal.

Enable builders to publish to environments such as QA, Test before publishing to Prod.

Sometimes a part of a dashboard only makes sense to show once the user has selected an input.

Currently Embeddable uses UTC by default (e.g. when aggregating results by day / week / etc.). We plan to support supplying a timezone, per dashboard session, so each user can see the results in the timezone that makes sense for them. This will also involve making the caching layer timezone-aware.

Make it easier for Embeddable builders to organise their Embeddables using folders.

Something to ease a component prop migration, or to create a template in case we go into the hundreds of dashboards. E.g. a basic import/export JSON endpoint to configure an Embeddable

Like the existing code versioning, enable users to roll back to a previously published version of an Embeddable.

Being able to test out new chart / component updates in, for example, a QA/dev environment, without breaking the main version of a dashboard. E.g. you may have code changes in a development branch which you then want to push to the dev Environment. You then makes changes to a dashboard in "Dev" environment (but these changes don't override dashboard in "Prod" environment, i.e. you can still make patch changes to Prod version of dashboard in canvas). But once dev dashboard is ready you can perhaps overwrite Prod version of canvas with CI version

For each chosen dimension / measure, based on the type, allow specifying a number of additional settings (e.g. title / granularity / rounding / etc.) E.g. for a table component, that takes a list of dimensions as its input, it would be nice to be able to say that for each chosen dimension there is also an optional text input where they can override the column title, as well as a number input for overriding the default width.

Currently you might build a dashboard in dev that you then want to "push" to a live workspace

It would be really useful to be able to use Embeddable + Cube to build forecasting dashboards

This will allow you to dynamically control which dimension or measure to segment or aggregate by. E.g. you could have a dropdown containing a list of dimensions or measures, and then when users switch to another dimension or measure, all the charts update to show that dimension or measure.