[pickers] Simplify the API of the field hooks #11371
Conversation
flaviendelangle
added
component: pickers
| import { TextFieldProps } from '@mui/material/TextField'; | ||
| import { UseFieldResponse } from './useField'; | ||
|
|
||
| export const useConvertFieldResponseIntoMuiTextFieldProps = < |
There was a problem hiding this comment.
With #10649 this will convert either to the MuiTextField or PickersTextField format.
flaviendelangle
changed the title
useClearableField
|
Deploy preview: https://deploy-preview-11371--material-ui-x.netlify.app/ Updated pages: |
flaviendelangle
changed the title
useClearableField
github-actions
bot
added
the
PR: out-of-date
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
github-actions
bot
removed
the
PR: out-of-date
packages/x-date-pickers-pro/src/MultiInputDateRangeField/MultiInputDateRangeField.tsx
Outdated
Show resolved
Hide resolved
flaviendelangle
force-pushed
the
clearable-cleanup
branch
from
40b549f to
d3a1866
Compare
flaviendelangle
force-pushed
the
clearable-cleanup
branch
from
d3a1866 to
6289e28
Compare
| :::success | ||
| The following breaking changes only impact you if you are using hooks like `useDateField` to build a custom UI. | ||
|
|
||
| If you are just using the regular field components, then you can safely skip this section. |
There was a problem hiding this comment.
Just an idea when reading it: differences betweeen sections/subsection is not always super clear. This could be a helper. Maybe better to add that kind of stuff after the first stable, when the migration guide structure will stop moving.
| If you are just using the regular field components, then you can safely skip this section. | |
| If you are just using the regular field components, then you can safely [skip this section](#date-management). |
There was a problem hiding this comment.
That's a nice idea
Maybe we can do it on the whole migration guide at the end of the alpha to make sure we don't have outdated things
github-actions
bot
added
the
PR: out-of-date
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
github-actions
bot
removed
the
PR: out-of-date
| @@ -28,7 +25,7 @@ type DateRangeFieldComponent = (<TDate>( | |||
| */ | |||
| const SingleInputDateRangeField = React.forwardRef(function SingleInputDateRangeField<TDate>( | |||
| inProps: SingleInputDateRangeFieldProps<TDate>, | |||
| ref: React.Ref<HTMLDivElement>, | |||
| inRef: React.Ref<HTMLDivElement>, | |||
There was a problem hiding this comment.
Nitpick: Was there a need to rename the prop? I can't see a naming conflict anywhere. 🙈
There was a problem hiding this comment.
No indeed, I forgot to remove it 😬
There was a problem hiding this comment.
👌 Just confirming that this is probably the case in most if not all field components. 😉
Extracted from #10649
You can have a look at the migration guide for more information