-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[pickers] Improve the DX of custom fields #14496
Comments
Exploration of a Base UI DX (for built in editing behavior)GoalsThe content below describes what the DX could look like in 12-18 months, once we won't be supporting
import { DateField } from '@mui/x-date-pickers/DateField'
return <DateField />
Problem of the current DXToo many conceptsOnce the The goal is basically to merge Difficult to know where each element returned by
|
Exploration of the hook API (for custom editing behavior)Utilities
|
Exploration of a better doc structureWIP |
We currently have a several examples on how to create fields with custom UIs (using browser primitives, using Joy UI, ...) and we have 2 demos on how to create fields with custom behaviors (one with a Button, one with an Autocomplete).
The goal of this issue is to improve the 2nd type of demo and to create a few new ones.
Here are the planned work:
Enhancements
splitFieldInternalAndForwardedProps
public #14515InputProps.endAdornment
) and instead pass a prop likeonOpen
to the field component and let him handle the opening UI (the built-in fields would then handle slots likeopeningButton
,openingIcon
andinputAdornment
themselves)Missing doc sections
useValidation
useSplitFieldProps
useParsedFormat
usePickersContext
Recipes for custom behavior field
Autocomplete
Field demo #15165Search keywords:
The text was updated successfully, but these errors were encountered: