[pickers] Replace the TDate generic with PickerValidDate in every type / interface

[flaviendelangle]

Part of #13188

Small history

• When we migrated the project from @mui/lab, after some cleaning we ended up with two generics:

  • TInputDate: the format supported by props.value which was the format parseable by the lib (usually something like Date | Dayjs | string | undefined)
  • TDate: the format of the date library (something like Dayjs)

  See [pickers] Rework TDate, TInputDate, TValue and TInputValue generics #4617 for the full context

• In version 6.0.0, we dropped the support for unparsed dates

  People now have to pass value={dayjs('2022-04-17')}, formats like value="2022-04-17" no longer work.

  See [pickers] Do not support unparsed date formats anymore #6170 for the full context

• In version 7.0.0, we created a new type PickerValidDate that each adapter enriches with its date format.
  The interfaces in the application can now limit the valid values of TDate to be TDate extends PickerValidDate.

  So the typing now looks something like this:

  interface DatePickerProps<TDate extends PickerValidDate> {
    value: TDate | null;
  }
  
  function DatePicker<TDate extends PickerValidDate>(props: DatePickerProps<TDate>) { ... }

Proposal

In a real application you have only one adapter so only one value added to PickerValidDate, which means we can remove the TDate generic and have the following:

interface DatePickerProps {
  value: PickerValidDate | null;
}

function DatePicker(props: DatePickerProps) { ... }

Search keywords:

[github-actions]

This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.