[docs] Fix type arguments in Custom Field page #12619
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In v7, the
UseDateFieldProps
andBaseSingleInputFieldProps
require an additionalTEnableAccessibleFieldDOMStructure extends boolean
type argument.mui-x/packages/x-date-pickers/src/DateField/DateField.types.ts
Lines 24 to 27 in ef40e06
mui-x/packages/x-date-pickers/src/models/fields.ts
Lines 168 to 174 in ef40e06
The latest "Custom field" documentation page is still using the old v6 version. TypeScript reports the following errors: