Charts and components
Remarkable Pro
Change log

Remarkable Pro — Changelog

All notable changes to @embeddable.com/remarkable-pro (opens in a new tab) are documented here. Releases follow Semantic Versioning (opens in a new tab).

Install the latest version:

npm install @embeddable.com/remarkable-pro

Changelog entries


v0.5.02026-09-04
  • Fixed date ranges being anchored in UTC rather than the dashboard's configured timezone. Both custom date picks and built-in presets (Today, Yesterday, Last 7 days, etc.) now compute boundaries using the dashboard's own timezone throughout, so the data returned always matches the calendar day the user selected in their local timezone.
v0.4.22026-09-01
  • Fixed DateRangePickerCustomPro and DateRangePickerPresetsPro resolving manually picked dates to the wrong calendar day when clientContext.timezone differed from the viewer's browser timezone. getTimeRangeFromDateRange now uses clientContext.timezone when projecting selected dates, matching the existing preset behaviour. Two edge cases are also resolved: a near-midnight end-of-day UTC timestamp could tip into the next calendar day after timezone projection (now normalised back to its own day-start), and an incomplete range (single click, to undefined) was defaulting to to the current time instead of the picked day.
v0.4.12026-08-27
  • Fixed DateRangePickerPresetsPro not syncing when selectedValue changes to a custom {from, to} range. Unapplied date range edits are now also discarded when the picker closes without pressing Apply.
v0.4.02026-08-26
  • MultiSelectFieldPro now supports an opt-in select all / deselect all option, controlled by a new 'Display "select / deselect all"' input (off by default). The option only appears when the loaded values are fewer than the maximum options limit, ensuring the full list is known to be complete.
v0.3.272026-08-18
  • Fixed DateRangePickerPresetsPro custom calendar going out of sync with selectedValue. The trigger label correctly reflected the latest bound value, but the internal dateRange state (used by the calendar and the Apply button) was not kept in sync — causing the Custom view to open with nothing selected and Apply enabled when a preset was active, and an externally updated selectedValue to update the label without updating the calendar grid. dateRange is now initialised from the resolved time range on mount and re-synced whenever selectedValue changes.
v0.3.262026-08-04
  • Exposed CSS variables for canvas overlays, enabling custom styling for overlay positioning, sizing, spacing, colours, actions, responsive layouts, and configurator forms.
v0.3.252026-08-03
  • Fixed syncDefaultFilters in FilterBuilderPro and FilterBuilderWithGroupingPro not re-applying a previously adopted defaultFilters value after the filter list was cleared. Deleting the last filter emits null, which was leaving stale adoption state behind — so pushing the same clause back in from the host was silently ignored. The host can now revert to or re-push a filter set after it has been cleared, and it will be re-applied as expected.
v0.3.242026-07-31
  • FilterBuilderWithGroupingPro now dispatches embeddable-user-interaction events on user-driven edits (top-level and group-level), matching FilterBuilderPro. An optional trackingId input and componentName have been added for consistency with other trackable components.
v0.3.232026-07-31
  • FilterBuilderPro and FilterBuilderWithGroupingPro now support a new opt-in **Track default filters** (syncDefaultFilters) setting. When enabled, the component tracks host-driven changes to its bound defaultFilters after mount — allowing the host to update or reset the filter at runtime (e.g. switching between or reverting to saved filter sets) without remounting the embed. The component's own onChange echo and null/undefined values are ignored so in-progress edits are preserved, and a well-formed empty clause resets the filters. When disabled (the default), behaviour is unchanged: defaultFilters only seeds the initial value.
v0.3.222026-07-28
  • Added a standardised embeddable-user-interaction browser event that all Pro chart components dispatch on click interactions. The event fires on the window object and carries a consistent payload including componentName, an optional trackingId, and the clicked dimension, dimensionValue, dimensionTimeRange, group-by dimension, and measure values — providing a single chart-agnostic way to observe and react to user interactions across all Pro charts. An optional trackingId input has been added to affected chart components so specific chart instances can be identified in event listeners.
  • Improved click-event payload consistency: when a click resolves to a time range, dimensionValue is now set to undefined to avoid duplicating the raw value alongside dimensionTimeRange.