[pickers] Allow to refuse ranges that contains at least one disabled date about mui-x HOT 4 OPEN

@bruns6077 interesting use case indeed!
@LukasTy do you know if we can support such behavior? I guess we could utilize the shouldDisabelDate method to define disabled days based on the currently selected (start-)range and the definitely disabled ones, but this can be potentially expensive.
WDYT?

from mui-x.

@michelengelen Yeah i think also that this could be expensive. But what about the custom day rendering then ?

from mui-x.

Great suggestion for disabled dates behavior.
Just one clarification - I believe that if we add a flag to control it, then this behavior should be turned off by default to avoid a breaking behavior change.

As for the custom day rendering, have you tried passing your own component to the day slot? 🤔

And for the current option to implement the requested custom behavior - yes, using shouldDisableDate seems like the single option at the moment. 🤷

I'm moving this issue to our board for grooming to discuss the disabled behavior extending. 😉

from mui-x.

@LukasTy our discussion works great for DateRangePicker.
But what about DateTimeRangePicker? We can't test every time in the range to check if some are disabled.

Would you be OK to only add the prop to DateRangePicker and think about the lower level API for the DateTimeRangePicker?
Or should we re-evaluate our approach?

BTW the other issue solved by a lower level API like isRangeValid is #8868

from mui-x.