[calebporzio]

The scenario

Flux Pro is adding a datetime picker with a range mode. Range values need to round-trip through Livewire with their times intact.

The problem

Flux\DateRange only stores dates. Its synth serializes Y-m-d, so binding it to a datetime range drops the times.

The solution

This adds Flux\DateTimeRange, a CarbonPeriod subclass like DateRange, plus a Livewire synth that serializes both ends as Y-m-d\TH:i (the format the datetime picker and native datetime-local inputs use).

public ?DateTimeRange $window;

$this->window = new DateTimeRange(now()->setTime(22, 0), now()->addDay()->setTime(2, 0));

• The range's timezone travels in the synth metadata, so it survives requests and new selections are parsed in the same timezone.
• A range needs both ends: partial or empty values hydrate to null, and unsetting either end clears it.
• unwrapForValidation exposes start/end strings for range.start style rules.
• It works with whereBetween() like any CarbonPeriod.

Flux Pro PR: https://github.com/livewire/flux-pro/pull/588
Docs PR: https://github.com/livewire/flux-docs/pull/244

Verification

• Round-trip checks (timezone preserved, nested set, unset, whole-object hydrate, null/partial values, validation unwrap)
• Flux Pro datetime picker Playwright tests binding a DateTimeRange property (pre-filled and empty)

🤖 Generated with Claude Code