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 🥺

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

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.

End users can download their dashboard as a PDF

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.

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.

Sometimes variables are being set as one type (e.g. text or boolean or number) but we want to use them as an input for a component that expects a different type. Automatic converting or casting of types (where it makes sense) could significantly reduce this problem. This problem comes up regularly when a control is designed to be reusable and thus its events always output strings, even though the dimension it came from might be a number of boolean, etc.

Sometimes it's useful for users to focus in on a chart on a dashboard and see it full screen

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

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.

To make building dashboards in the no-code builder easier, we'll introduce the concept of 'containers' to layout components on the canvas

It would be useful to be able to clone a dashboard from the live workspace to local dev preview so that it could be worked on locally

We will support the option for customers to self-host Embeddable.