Feature Ideas

Right now the output folder for build, and the input folder for push, are hard-coded. It'd be useful for some teams with more complicated CI/CD setups if they could specify those folders, in order to facilitate things like "run the build, then tarball it, then move it somewhere else, then later on run the push from that somewhere else" eg: embeddable:build --output /some/path and embeddable:push --input /some/path

It would be nice to have a button that allowed the end users the option to refresh the data in their dashboards, without refreshing the page.

Great for visualising pipelines for marketing / sales

This would be a cool addition to the out-of-the-box charts

Provide a read-only API endpoint that allows customers to introspect dashboards (embeddables) and retrieve the list of variables/filters used within them. This would enable automated validation to ensure standardized “well-known” variable names are consistently applied across dashboards, support governance in environments without code review, and allow applications to dynamically discover and integrate with available dashboard variables which is particularly useful if dashboards are versioned or published via code in the future.

It would be nice to be able to show the totals for the table component

Adding a second row dimension enables you to drill into the data for a particular row i.e. when you click a row, it will show the underlying values, based on the second dimension.

Configurable tooltips to add additional metrics on hover (e.g. bar chart shows # Sales, tooltip shows $ Sales, # Customers) Configurable tooltip for function (variance actual vs. %) Metric tooltips - hover over the name of the tooltip to bring back metadata about the metric (e.g. “description” field from the data model)

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.

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

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

End users can download their dashboard as a PDF

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

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