Date Picker
Date pickers let the user select a date.
Date pickers let the user select a date. Date pickers are displayed with:
- Dialogs on mobile
- Text field dropdowns on desktop
Requirements
This component relies on the date management library of your choice. It supports date-fns, luxon, dayjs, moment and any other library via a public dateAdapter
interface.
Please install any of these libraries and set up the right date engine by wrapping your root (or the highest level you wish the pickers to be available) with LocalizationProvider
:
// or @material-ui/lab/Adapter{DayJS,Luxon,Moment} or any valid date-io adapter
import AdapterDateFns from '@material-ui/lab/AdapterDateFns';
import LocalizationProvider from '@material-ui/lab/LocalizationProvider';
function App() {
return (
<LocalizationProvider dateAdapter={AdapterDateFns}>...</LocalizationProvider>
);
}
Basic usage
The date picker is rendered as a modal dialog on mobile, and a textbox with a popup on desktop.
<LocalizationProvider dateAdapter={AdapterDateFns}>
<DatePicker
label="Basic example"
value={value}
onChange={(newValue) => {
setValue(newValue);
}}
renderInput={(params) => <TextField {...params} />}
/>
</LocalizationProvider>
Static mode
It's possible to render any date picker without the modal/popover and text field. This can be helpful when building custom popover/modal containers.
<LocalizationProvider dateAdapter={AdapterDateFns}>
<StaticDatePicker
displayStaticWrapperAs="desktop"
openTo="year"
value={value}
onChange={(newValue) => {
setValue(newValue);
}}
renderInput={(params) => <TextField {...params} />}
/>
</LocalizationProvider>
Responsiveness
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.
Localization
Use LocalizationProvider
to change the date-engine locale that is used to render the date picker. Here is an example of changing the locale for the date-fns
adapter:
Jalali calendar system
Install date-fns-jalali
and use @date-io/date-fns-jalali
adapter to support Jalali calendar.
<LocalizationProvider dateAdapter={AdapterJalali}>
<DatePicker
mask="____/__/__"
value={value}
onChange={(newValue) => setValue(newValue)}
renderInput={(params) => <TextField {...params} />}
/>
</LocalizationProvider>
Views playground
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.
<LocalizationProvider dateAdapter={AdapterDateFns}>
<StaticDatePicker
orientation="landscape"
openTo="day"
value={value}
shouldDisableDate={isWeekend}
onChange={(newValue) => {
setValue(newValue);
}}
renderInput={(params) => <TextField {...params} />}
/>
</LocalizationProvider>
Sub-components
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.).
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.
<LocalizationProvider dateAdapter={AdapterDateFns}>
<DesktopDatePicker
label="Custom input"
value={value}
onChange={(newValue) => {
setValue(newValue);
}}
renderInput={({ inputRef, inputProps, InputProps }) => (
<Box sx={{ display: 'flex', alignItems: 'center' }}>
<input ref={inputRef} {...inputProps} />
{InputProps?.endAdornment}
</Box>
)}
/>
</LocalizationProvider>
Customized day rendering
The displayed days are customizable with the renderDay
function prop.
You can take advantage of the PickersDay component.
<LocalizationProvider dateAdapter={AdapterDateFns}>
<StaticDatePicker
displayStaticWrapperAs="desktop"
label="Week picker"
value={value}
onChange={(newValue) => {
setValue(newValue);
}}
renderDay={renderWeekPickerDay}
renderInput={(params) => <TextField {...params} />}
inputFormat="'Week of' MMM d"
/>
</LocalizationProvider>
Dynamic data
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.
<LocalizationProvider dateAdapter={AdapterDateFns}>
<DatePicker
label="Helper text example"
value={value}
onChange={(newValue) => {
setValue(newValue);
}}
renderInput={(params) => (
<TextField {...params} helperText={params?.inputProps?.placeholder} />
)}
/>
</LocalizationProvider>