The date picker component is designed and optimized for the device it runs on.
The MobileDatePicker component works best for touch devices and small screens.
The DesktopDatePicker component works best for mouse devices and large screens.
By default, the DatePicker component renders the desktop version if the media query @media (pointer: fine) matches.
This can be customized with the desktopModeMediaQuery prop.
There are certain caveats when testing pickers, please refer to this section for more information.
Form props
The date picker component can be disabled or read-only.
Localization
Use LocalizationProvider to change the date-library locale that is used to render the date picker.
See the documentation page about localization for more details.
Jalali calendar system
Install date-fns-jalali and use @date-io/date-fns-jalali adapter to support Jalali calendar.
It's possible to combine year, month, and date selection views. Views will appear in the order they're included in the views array.
Landscape orientation
For ease of use, the date picker will automatically change the layout between portrait and landscape by subscription to the window.orientation change. You can force a specific layout using the orientation prop.
Some lower-level sub-components (CalendarPicker, MonthPicker, and YearPicker) are also exported. These are rendered without a wrapper or outer logic (masked input, date values parsing and validation, etc.).
April 2022
SMTWTFS
Custom input component
You can customize the rendering of the input with the renderInput prop. Make sure to spread ref and inputProps correctly to the custom input component.
Sometimes it may be necessary to display additional info right in the calendar. Here's an example of prefetching and displaying server-side data using the onMonthChange, loading, and renderDay props.
Helper text
You can show a helper text with the date format accepted.
mm/dd/yyyy
<LocalizationProviderdateAdapter={AdapterDayjs}><DatePickerlabel="Helper text example"value={value}onChange={(newValue)=>{setValue(newValue);}}renderInput={(params)=>(<TextField{...params}helperText={params?.inputProps?.placeholder}/>)}/></LocalizationProvider>