[Lisa18289]

Lists of logs, backups or cronjob runs can now be narrowed to a time window instead of whole days. dateRangeOptions={{ granularity: "minute" }} replaces the range calendar with start date, start time, end date and end time fields, in the filter popover and in the "All filters" modal. The default stays "day", so existing lists don't change.

A date without a time covers its whole day, an end time its whole minute, and an empty date leaves that side open. Times are local wall-clock times (CalendarDateTime). Changes apply as they are typed, as long as the range is valid; otherwise the filter keeps the last valid range. A range that ends before it starts shows one error below all fields, whichever field was filled first, and a date outside minValue/maxValue shows its field's error. dateRangeOptions is a union now, so the calendar-only props are a type error with "minute".

Worth a look: the active filter chip now formats with the Flow locale instead of the browser's (still numeric, e.g. 9/2/2025, with , 14:30 for a time), for both granularities, which changes the existing "filtered" baseline. The new visual scenarios are gated on 1.5.0 for cross-version runs. resolveDateRangeFilterValue is exported (also from flr-universal and the Vue package) so a loader filtering on the server resolves a filter value to the same bounds.

The Vue List gets the same fields. The rules live in components-base, so both bindings run them: the comparison (a CalendarDateTime or ZonedDateTime cell now counts as a date), which typed input applies, and the chip text. e2e/list-parity has four new scenarios, and remote-dom-demo a Vue list-date-range demo.

Two fixes on the way. Setting a date range didn't notify the filter's listeners, so a list with a loader kept its batches; in Vue it kept showing the old range's rows. And the parity normalizer numbered Vue's useId before react-aria's ids within one aria-describedby, instead of left to right.

Closes #3375

🤖 Generated with Claude Code

[github-actions]

🚀 Preview Deployment

Preview environments are ready:

Type	URL
docs	pr-3388.docs.review.flow-components.de
storybook	pr-3388.storybook.review.flow-components.de

Images:

• docs: ghcr.io/mittwald/flow/docs:pr-3388
• storybook: ghcr.io/mittwald/flow/storybook:pr-3388

[github-actions]

❌ Visual Regression Tests Failed

At least one shard did not pass. If snapshots differ from the committed baselines, download the visual-diffs-* artifacts from this run to inspect the actual/diff images (a shard that failed before comparison, e.g. during install or browser setup, leaves none).

If the differences are intentional, update the baselines by adding the update-screenshots label to the PR.

Run details