[pickers] New component: TimeRangePicker

[ErnestBrandi]

Benchmarks

• https://demo.mobiscroll.com/jquery/range/time-range#

[michaldudak]

We don't have it on the roadmap as of now. However, if we see significant interest in the community, we may consider creating one.

Edit: it's in our roadmap, and trying to find bandwidth to implement it.

[am-vishal]

we need time range picker in @mui something like this.
I found many people facing similar issues.
https://stackoverflow.com/questions/72811784/from-time-and-to-time-validation-in-react-dropdown-react-datepicker-hour

[flaviendelangle]

Small update here.
We know that a lot of people are waiting for this feature and it remains one of our top priority.

The team is currently rebuilding the input part of the pickers from scratch to provide a better experience.
We should be able to soon release a first documented (but still unstable) version of those components soon.
You can find a basic internal documentation of those components here if you are curious.

The plan is then to create new keyboard-only components from time range and date time range in the coming weeks.
And then to build new pickers around them, just like we plan to migrate the already existing pickers to those new components.

In summary the TimeRangePicker will come in two steps:

1. It's keyboard-only component (probably by the end of October with an Unstable_ prefix)
2. It's full picker with the calendar views (probably at the beginning of 2023, maybe before with an Unstable_ prefix)

[flaviendelangle]

As mentioned a few days ago, we now have a new component for date time range editing called MultiInputTimeRangeField (very long name, but a SingleInputTimeRangeField is in the pipeline).

The documentation is available here
It is still very early-stage but will serve as the baseline for the future TimeRangePicker.
So the more feedback we have to improve it, the easier it will be to build this new picker.

[ngouy]

@michaldudak could you put a hard number on if we see significant interest in the community, we may consider creating one. please?

Some might consider 700+ as significant, some other not. Curious on the number you have in mind in these situations

[flaviendelangle]

We don't have fixed number because it depends a lot on the complexity of the feature.
A small feature might be created after just a dozen up-votes, a whole new set of component will of course require more traction.
For the TimeRangePicker, it's under development 👍

[oliviertassinari]

In https://mui.com/blog/mui-x-v8-alpha-zero/ we communicated that MUI X v8.0 aims to include this issue.