[pickers] Replace the Picker prefix in the view component by Calendar (eg: MonthPicker => MonthCalendar)

[flaviendelangle]

Part of #4484

I'll add the detailed breaking changes later.
But here is the list of the renaming:

• CalendarPicker => DateCalendar (we can discuss naming it simply Calendar if you want, in which case the range version would be RangeCalendar and not DateRangeCalendar which would match Spectrum's naming)
• CalendarPickerSkeleton => DayCalendarSkeleton
• MonthPicker => MonthCalendar
• YearPicker => YearCalendar

Follow up:

• Rename ClockPicker => Clock

Changelog

Breaking changes

• The view components allowing to pick a date or parts of a date without an input have been renamed to better fit their usage:

  -<CalendarPicker {...props} />
  +<DateCalendar  {...props} />

  -<DayPicker {...props} />
  +<DayCalendar  {...props} />

  -<CalendarPickerSkeleton {...props} />
  +<DayCalendarSkeleton  {...props} />

  -<MonthPicker {...props} />
  +<MonthCalendar  {...props} />

  -<YearPicker {...props} />
  +<YearCalendar  {...props} />

• Component names in the theme have changed as well:

  -MuiCalendarPicker: {
  +MuiDateCalendar: {

  -MuiDayPicker: {
  +MuiDayCalendar: {

  -MuiCalendarPickerSkeleton: {
  +MuiDayCalendarSkeleton: {

  -MuiMonthPicker: {
  +MuiMonthCalendar: {

  -MuiYearPicker: {
  +MuiYearCalendar: {

[mui-bot]

These are the results for the performance tests:

Test case	Unit	Min	Max	Median	Mean	σ
Filter 100k rows	ms	479	736.6	608.4	605.82	93.101
Sort 100k rows	ms	572.4	971.1	803.9	779.02	149.69
Select 100k rows	ms	181.7	244.4	210.6	208.9	22.088
Deselect 100k rows	ms	129.7	300	192.2	193.48	58.572

Generated by 🚫 dangerJS against 2720982

[joserodolfofreitas]

Sounds great! I think we're all solid on the use of Calendar as a prefix.

As for DateCalendar => Calendar.
I think DateCalendar feels more consistent with our naming system (by using Calendar always as a Prefix to identify that's a date input view). Btw, would it make sense if it was named DayCalendar ?

On the other hand, I think RangeCalendar sounds like a better name for its situation.

Another thought regarding this naming: If we're ever to implement a scheduler component, would it use this calendar component (obviously with some customizations) ? or would it have its own implementation?

[flaviendelangle]

Btw, would it make sense if it was named DayCalendar ?

For me our current naming differentiate the date (day + month + year) and the day
We have a DayCalendar (DayPicker right now) which is private and only allow the selection of the day.
Whereas DateCalendar (CalendarPicker right now) allows the selection of the day, the year and the month

Another thought regarding this naming: If we're ever to implement a scheduler component, would it use this calendar component (obviously with some customizations) ? or would it have its own implementation?

Hard to say, maybe our DayPicker could be flexible enough at some point but I'm not sure.
Some internals would probably be shared though.

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[LukasTy]

Could we also include breaking changes mention in the PR description so it would be picked up by release script? 🤔

[flaviendelangle]

Could we also include breaking changes mention in the PR description so it would be picked up by release script? thinking

Sure, I just waited for a confirmation on the nomenclature, I'll write those

[LukasTy]

Good job, great result! 👍