Feature Ideas

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

Some teams might have their own local databases that they want to use when building locally, instead of using the connections that are set up via the connections API.

Currently the tooltip behaviour in Remarkable is to show all the values (for example in a multi-line chart this would mean all values for a particular point on the x-axis) but in some cases it would be useful to be able to toggle to just show either one or many data points. You can override the tooltip behaviour via theming but this would be nice to have as OOTB behaviour

E.g. ability to switch dimensions into rows/columns for the end user

This is a really nice feature to enable end-users to zoom in on a specific period (for example)

This would enable end users to search/filter the table easily

When you go under a certain number, chartjs automatically shows ' 0.5' increments on charts, which don't really make sense if the measure data being shown isn't type FLOAT

Currently we store the old model / component versions in Embeddable. While it's super useful to be able to see these generally, sometimes a dashboard version might be saved accidentally and then that version can't be deleted. The model / component versions can also clutter the dropdown a bit as well so would be handy to have a way to review / tidy these.

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

Currently dataset filters all use simple AND across each filter. It is, however, common that you might want to use OR instead, or a nesting thereof.

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