This repository was archived by the owner on Jul 19, 2025. It is now read-only.
v4.0.0-alpha.9
Pre-release
Pre-release
·
57 commits
to next
since this release
Breaking changes ⚠️
Migrate from <Popover /> to <Popper /> for desktop components.
We migrated our components to the core Popper + TrapFocus. Related to this all the components will not block scroll from now and also PopoverProps was removed in favor of PopperProps.
[typescript] Generic date type (#1966)
We got rid of dynamically attaching @date-io/type module declaration for the adapter's date engine type. From now on pickers will automatically infer the type of value or onChange props. But it is also possible to force using pickers with generic JSX components notation.
<DatePicker<Date>
// You can pass any value right here that can be parsed
value={null}
onChange={newValue => newValue?.getDate()}
/>Change date selection flow (#1923)
- From now on we will dispatch
onChangewhen each view is filled (when the next view needs to open). This allows the developer to understand which value is already filled and also improves UX with.Cancelbutton – if cancel clicked already filled part will be saved. (closes #1909) autoOkprop was removed and now picker will automatically close after selection for Desktop mode. It is possible to control this behavior with the newdisableCloseOnSelectProp(closes #1651)
Fixes / Enhancments 🐛
- Add missing props for DateRangePickerToolbar (#1914) @fhessenberger
- [typescript] Fix theme overrides type failing @bopfer
- [YearSelection] Do not call
shouldDisableDateon year selection view for each year. (#1954) - [DateRangePicker] Fix not working
renderDayprop (#1953) - [DateTimePicker] Always show arrow switcher in clock (#1949)
- [material design] Replace theme.palette.text.hint with theme.palette.text.secondary (#1952)
- [docs] Fix crash on DatePicker 'Customization' example (#1904) @bertrandp
- [docs] Improve Responsiveness sections (#1884) @xiaoyu-tamu
- [docs] Fix crash on DatePicker 'Customization' example (#1904) @bertrandp