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-proChangelog 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
DateRangePickerCustomProandDateRangePickerPresetsProresolving manually picked dates to the wrong calendar day whenclientContext.timezonediffered from the viewer's browser timezone.getTimeRangeFromDateRangenow usesclientContext.timezonewhen 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,toundefined) was defaultingtoto the current time instead of the picked day.
v0.4.12026-08-27
- Fixed
DateRangePickerPresetsPronot syncing whenselectedValuechanges 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
MultiSelectFieldPronow 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
DateRangePickerPresetsProcustom calendar going out of sync withselectedValue. The trigger label correctly reflected the latest bound value, but the internaldateRangestate (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 updatedselectedValueto update the label without updating the calendar grid.dateRangeis now initialised from the resolved time range on mount and re-synced wheneverselectedValuechanges.
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
syncDefaultFiltersinFilterBuilderProandFilterBuilderWithGroupingPronot re-applying a previously adopteddefaultFiltersvalue after the filter list was cleared. Deleting the last filter emitsnull, 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
FilterBuilderWithGroupingPronow dispatchesembeddable-user-interactionevents on user-driven edits (top-level and group-level), matchingFilterBuilderPro. An optionaltrackingIdinput andcomponentNamehave been added for consistency with other trackable components.
v0.3.232026-07-31
FilterBuilderProandFilterBuilderWithGroupingPronow support a new opt-in **Track default filters** (syncDefaultFilters) setting. When enabled, the component tracks host-driven changes to its bounddefaultFiltersafter 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 ownonChangeecho andnull/undefinedvalues are ignored so in-progress edits are preserved, and a well-formed empty clause resets the filters. When disabled (the default), behaviour is unchanged:defaultFiltersonly seeds the initial value.
v0.3.222026-07-28
- Added a standardised
embeddable-user-interactionbrowser event that all Pro chart components dispatch on click interactions. The event fires on thewindowobject and carries a consistent payload includingcomponentName, an optionaltrackingId, and the clickeddimension,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 optionaltrackingIdinput 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,
dimensionValueis now set toundefinedto avoid duplicating the raw value alongsidedimensionTimeRange.