Merge branch 'master' into remove-utils-and-value-params-from-transla…

…tions
mui · arthurbalduini · Oct 29, 2024 · Oct 15, 2024 · Oct 15, 2024 · Oct 15, 2024
commit 81051706a7b7ba5e799ea3ab14f884e8093bd7dd
diff --git a/packages/x-date-pickers/src/internals/components/PickersProvider.tsx b/packages/x-date-pickers/src/internals/components/PickersProvider.tsx
@@ -1,4 +1,5 @@
 import * as React from 'react';
+import { PickerOwnerState, PickerValidDate } from '../../models';
 import { PickersInputLocaleText } from '../../locales';
 import { LocalizationProvider } from '../../LocalizationProvider';
 
@@ -13,8 +14,8 @@ export const PickersPrivateContext = React.createContext<PickersPrivateContextVa
  *
  * @ignore - do not document.
  */
-export function PickersProvider(props: PickersFieldProviderProps) {
-  const { contextValue, localeText, children } = props;
+export function PickersProvider<TDate extends PickerValidDate>(props: PickersProviderProps<TDate>) {
+  const { contextValue, privateContextValue, localeText, children } = props;
 
   return (
     <PickersContext.Provider value={contextValue}>
@@ -25,9 +26,10 @@ export function PickersProvider(props: PickersFieldProviderProps) {
   );
 }
 
-interface PickersFieldProviderProps {
+export interface PickersProviderProps<TDate extends PickerValidDate> {
   contextValue: PickersContextValue;
-  localeText: PickersInputLocaleText | undefined;
+  privateContextValue: PickersPrivateContextValue;
+  localeText: PickersInputLocaleText<TDate> | undefined;
   children: React.ReactNode;
 }
 

diff --git a/docs/data/migration/migration-pickers-v7/migration-pickers-v7.md b/docs/data/migration/migration-pickers-v7/migration-pickers-v7.md
 ## Stop passing `utils` and the date object to some translation keys

 Some translation keys no longer require `utils` and the date object as parameters, but only the formatted value as a string. The keys affected by this changes are: `clockLabelText`, `openDatePickerDialogue` and `openTimePickerDialogue`.
 If you have customized those translation keys, you have to update them following the examples bellow:

 - If you are setting a custom value in a picker component:
	## Stop passing `utils` and the date object to some translation keys

	Some translation keys no longer require `utils` and the date object as parameters, but only the formatted value as a string. The keys affected by this changes are: `clockLabelText`, `openDatePickerDialogue` and `openTimePickerDialogue`.
	If you have customized those translation keys, you have to update them following the examples bellow:
Check failure on line 321 in docs/data/migration/migration-pickers-v7/migration-pickers-v7.md GitHub Actions / runner / vale `[vale] reported by reviewdog 🐶 [MUI.NoBritish] Use the US spelling 'below' instead of the British 'bellow' Raw Output: {"message": "[MUI.NoBritish] Use the US spelling 'below' instead of the British 'bellow'", "location": {"path": "docs/data/migration/migration-pickers-v7/migration-pickers-v7.md", "range": {"start": {"line": 321, "column": 95}}}, "severity": "ERROR"}`

	- If you are setting a custom value in a picker component: