@mui/x-date-pickers-pro 8.0.0-beta.2 → 8.0.0

package/modern/MultiInputDateTimeRangeField/MultiInputDateTimeRangeField.d.ts

@@ -1,25 +0,0 @@
-import * as React from 'react';
-import { UseDateTimeRangeManagerReturnValue } from "../managers/index.js";
-import { MultiInputRangeFieldProps } from "../internals/utils/createMultiInputRangeField/index.js";
-import { MultiInputDateTimeRangeFieldClasses } from "./multiInputDateTimeRangeFieldClasses.js";
-export interface MultiInputDateTimeRangeFieldProps<TEnableAccessibleFieldDOMStructure extends boolean> extends MultiInputRangeFieldProps<UseDateTimeRangeManagerReturnValue<TEnableAccessibleFieldDOMStructure>> {
-  /**
-   * Override or extend the styles applied to the component.
-   */
-  classes?: Partial<MultiInputDateTimeRangeFieldClasses>;
-}
-type MultiInputDateTimeRangeFieldComponent = (<TEnableAccessibleFieldDOMStructure extends boolean = true>(props: MultiInputDateTimeRangeFieldProps<TEnableAccessibleFieldDOMStructure> & React.RefAttributes<HTMLDivElement>) => React.JSX.Element) & {
-  propTypes?: any;
-};
-/**
- * Demos:
- *
- * - [DateTimeRangeField](http://mui.com/x/react-date-pickers/date-time-range-field/)
- * - [Fields](https://mui.com/x/react-date-pickers/fields/)
- *
- * API:
- *
- * - [MultiInputDateTimeRangeField API](https://mui.com/x/api/multi-input-date-time-range-field/)
- */
-declare const MultiInputDateTimeRangeField: MultiInputDateTimeRangeFieldComponent;
-export { MultiInputDateTimeRangeField };

package/modern/MultiInputDateTimeRangeField/MultiInputDateTimeRangeField.js

@@ -1,255 +0,0 @@
-'use client';
-
-import PropTypes from 'prop-types';
-import { useDateTimeRangeManager } from "../managers/index.js";
-import {
-// The alias is needed to have the doc gen working.
-createMultiInputRangeField as createMultiInputDateTimeRangeField } from "../internals/utils/createMultiInputRangeField/index.js";
-import { getMultiInputDateTimeRangeFieldUtilityClass } from "./multiInputDateTimeRangeFieldClasses.js";
-/**
- * Demos:
- *
- * - [DateTimeRangeField](http://mui.com/x/react-date-pickers/date-time-range-field/)
- * - [Fields](https://mui.com/x/react-date-pickers/fields/)
- *
- * API:
- *
- * - [MultiInputDateTimeRangeField API](https://mui.com/x/api/multi-input-date-time-range-field/)
- */
-const MultiInputDateTimeRangeField = createMultiInputDateTimeRangeField({
-  name: 'MuiMultiInputDateTimeRangeField',
-  getUtilityClass: getMultiInputDateTimeRangeFieldUtilityClass,
-  useManager: useDateTimeRangeManager
-});
-MultiInputDateTimeRangeField.propTypes = {
-  // ----------------------------- Warning --------------------------------
-  // | These PropTypes are generated from the TypeScript type definitions |
-  // | To update them edit the TypeScript types and run "pnpm proptypes"  |
-  // ----------------------------------------------------------------------
-  /**
-   * 12h/24h view for hour selection clock.
-   * @default utils.is12HourCycleInCurrentLocale()
-   */
-  ampm: PropTypes.bool,
-  /**
-   * If `true`, the `input` element is focused during the first mount.
-   * @default false
-   */
-  autoFocus: PropTypes.bool,
-  /**
-   * Override or extend the styles applied to the component.
-   */
-  classes: PropTypes.object,
-  className: PropTypes.string,
-  component: PropTypes.elementType,
-  /**
-   * String displayed between the start and the end dates.
-   * @default "–"
-   */
-  dateSeparator: PropTypes.string,
-  /**
-   * The default value. Use when the component is not controlled.
-   */
-  defaultValue: PropTypes.arrayOf(PropTypes.object),
-  /**
-   * Defines the `flex-direction` style property.
-   * It is applied for all screen sizes.
-   * @default 'column'
-   */
-  direction: PropTypes.oneOfType([PropTypes.oneOf(['column-reverse', 'column', 'row-reverse', 'row']), PropTypes.arrayOf(PropTypes.oneOf(['column-reverse', 'column', 'row-reverse', 'row'])), PropTypes.object]),
-  /**
-   * If `true`, the component is disabled.
-   * When disabled, the value cannot be changed and no interaction is possible.
-   * @default false
-   */
-  disabled: PropTypes.bool,
-  /**
-   * If `true`, disable values after the current date for date components, time for time components and both for date time components.
-   * @default false
-   */
-  disableFuture: PropTypes.bool,
-  /**
-   * Do not ignore date part when validating min/max time.
-   * @default false
-   */
-  disableIgnoringDatePartForTimeValidation: PropTypes.bool,
-  /**
-   * If `true`, disable values before the current date for date components, time for time components and both for date time components.
-   * @default false
-   */
-  disablePast: PropTypes.bool,
-  /**
-   * Add an element between each child.
-   */
-  divider: PropTypes.node,
-  /**
-   * @default true
-   */
-  enableAccessibleFieldDOMStructure: PropTypes.bool,
-  /**
-   * Format of the date when rendered in the input(s).
-   */
-  format: PropTypes.string,
-  /**
-   * Density of the format when rendered in the input.
-   * Setting `formatDensity` to `"spacious"` will add a space before and after each `/`, `-` and `.` character.
-   * @default "dense"
-   */
-  formatDensity: PropTypes.oneOf(['dense', 'spacious']),
-  /**
-   * Maximal selectable date.
-   * @default 2099-12-31
-   */
-  maxDate: PropTypes.object,
-  /**
-   * Maximal selectable moment of time with binding to date, to set max time in each day use `maxTime`.
-   */
-  maxDateTime: PropTypes.object,
-  /**
-   * Maximal selectable time.
-   * The date part of the object will be ignored unless `props.disableIgnoringDatePartForTimeValidation === true`.
-   */
-  maxTime: PropTypes.object,
-  /**
-   * Minimal selectable date.
-   * @default 1900-01-01
-   */
-  minDate: PropTypes.object,
-  /**
-   * Minimal selectable moment of time with binding to date, to set min time in each day use `minTime`.
-   */
-  minDateTime: PropTypes.object,
-  /**
-   * Minimal selectable time.
-   * The date part of the object will be ignored unless `props.disableIgnoringDatePartForTimeValidation === true`.
-   */
-  minTime: PropTypes.object,
-  /**
-   * Step over minutes.
-   * @default 1
-   */
-  minutesStep: PropTypes.number,
-  /**
-   * Callback fired when the value changes.
-   * @template TValue The value type. It will be the same type as `value` or `null`. It can be in `[start, end]` format in case of range value.
-   * @template TError The validation error type. It will be either `string` or a `null`. It can be in `[start, end]` format in case of range value.
-   * @param {TValue} value The new value.
-   * @param {FieldChangeHandlerContext<TError>} context The context containing the validation result of the current value.
-   */
-  onChange: PropTypes.func,
-  /**
-   * Callback fired when the error associated with the current value changes.
-   * When a validation error is detected, the `error` parameter contains a non-null value.
-   * This can be used to render an appropriate form error.
-   * @template TError The validation error type. It will be either `string` or a `null`. It can be in `[start, end]` format in case of range value.
-   * @template TValue The value type. It will be the same type as `value` or `null`. It can be in `[start, end]` format in case of range value.
-   * @param {TError} error The reason why the current value is not valid.
-   * @param {TValue} value The value associated with the error.
-   */
-  onError: PropTypes.func,
-  /**
-   * Callback fired when the selected sections change.
-   * @param {FieldSelectedSections} newValue The new selected sections.
-   */
-  onSelectedSectionsChange: PropTypes.func,
-  /**
-   * If `true`, the component is read-only.
-   * When read-only, the value cannot be changed but the user can interact with the interface.
-   * @default false
-   */
-  readOnly: PropTypes.bool,
-  /**
-   * The date used to generate a part of the new value that is not present in the format when both `value` and `defaultValue` are empty.
-   * For example, on time fields it will be used to determine the date to set.
-   * @default The closest valid date using the validation props, except callbacks such as `shouldDisableDate`. Value is rounded to the most granular section used.
-   */
-  referenceDate: PropTypes.object,
-  /**
-   * The currently selected sections.
-   * This prop accepts four formats:
-   * 1. If a number is provided, the section at this index will be selected.
-   * 2. If a string of type `FieldSectionType` is provided, the first section with that name will be selected.
-   * 3. If `"all"` is provided, all the sections will be selected.
-   * 4. If `null` is provided, no section will be selected.
-   * If not provided, the selected sections will be handled internally.
-   */
-  selectedSections: PropTypes.oneOfType([PropTypes.oneOf(['all', 'day', 'empty', 'hours', 'meridiem', 'minutes', 'month', 'seconds', 'weekDay', 'year']), PropTypes.number]),
-  /**
-   * Disable specific date.
-   *
-   * Warning: This function can be called multiple times (for example when rendering date calendar, checking if focus can be moved to a certain date, etc.). Expensive computations can impact performance.
-   *
-   * @param {PickerValidDate} day The date to test.
-   * @param {string} position The date to test, 'start' or 'end'.
-   * @returns {boolean} Returns `true` if the date should be disabled.
-   */
-  shouldDisableDate: PropTypes.func,
-  /**
-   * Disable specific time.
-   * @param {PickerValidDate} value The value to check.
-   * @param {TimeView} view The clock type of the timeValue.
-   * @returns {boolean} If `true` the time will be disabled.
-   */
-  shouldDisableTime: PropTypes.func,
-  /**
-   * If `true`, the format will respect the leading zeroes (for example on dayjs, the format `M/D/YYYY` will render `8/16/2018`)
-   * If `false`, the format will always add leading zeroes (for example on dayjs, the format `M/D/YYYY` will render `08/16/2018`)
-   *
-   * Warning n°1: Luxon is not able to respect the leading zeroes when using macro tokens (for example "DD"), so `shouldRespectLeadingZeros={true}` might lead to inconsistencies when using `AdapterLuxon`.
-   *
-   * Warning n°2: When `shouldRespectLeadingZeros={true}`, the field will add an invisible character on the sections containing a single digit to make sure `onChange` is fired.
-   * If you need to get the clean value from the input, you can remove this character using `input.value.replace(/\u200e/g, '')`.
-   *
-   * Warning n°3: When used in strict mode, dayjs and moment require to respect the leading zeros.
-   * This mean that when using `shouldRespectLeadingZeros={false}`, if you retrieve the value directly from the input (not listening to `onChange`) and your format contains tokens without leading zeros, the value will not be parsed by your library.
-   *
-   * @default false
-   */
-  shouldRespectLeadingZeros: PropTypes.bool,
-  /**
-   * The props used for each component slot.
-   * @default {}
-   */
-  slotProps: PropTypes.object,
-  /**
-   * Overridable component slots.
-   * @default {}
-   */
-  slots: PropTypes.object,
-  /**
-   * Defines the space between immediate children.
-   * @default 0
-   */
-  spacing: PropTypes.oneOfType([PropTypes.arrayOf(PropTypes.oneOfType([PropTypes.number, PropTypes.string])), PropTypes.number, PropTypes.object, PropTypes.string]),
-  style: PropTypes.object,
-  /**
-   * The system prop, which allows defining system overrides as well as additional CSS styles.
-   */
-  sx: PropTypes.oneOfType([PropTypes.arrayOf(PropTypes.oneOfType([PropTypes.func, PropTypes.object, PropTypes.bool])), PropTypes.func, PropTypes.object]),
-  /**
-   * Choose which timezone to use for the value.
-   * Example: "default", "system", "UTC", "America/New_York".
-   * If you pass values from other timezones to some props, they will be converted to this timezone before being used.
-   * @see See the {@link https://mui.com/x/react-date-pickers/timezone/ timezones documentation} for more details.
-   * @default The timezone of the `value` or `defaultValue` prop is defined, 'default' otherwise.
-   */
-  timezone: PropTypes.string,
-  unstableEndFieldRef: PropTypes.oneOfType([PropTypes.func, PropTypes.object]),
-  unstableStartFieldRef: PropTypes.oneOfType([PropTypes.func, PropTypes.object]),
-  /**
-   * If `true`, the CSS flexbox `gap` is used instead of applying `margin` to children.
-   *
-   * While CSS `gap` removes the [known limitations](https://mui.com/joy-ui/react-stack/#limitations),
-   * it is not fully supported in some browsers. We recommend checking https://caniuse.com/?search=flex%20gap before using this flag.
-   *
-   * To enable this flag globally, follow the [theme's default props](https://mui.com/material-ui/customization/theme-components/#default-props) configuration.
-   * @default false
-   */
-  useFlexGap: PropTypes.bool,
-  /**
-   * The selected value.
-   * Used when the component is controlled.
-   */
-  value: PropTypes.arrayOf(PropTypes.object)
-};
-export { MultiInputDateTimeRangeField };

package/modern/MultiInputDateTimeRangeField/index.d.ts

@@ -1,5 +0,0 @@
-export { MultiInputDateTimeRangeField } from "./MultiInputDateTimeRangeField.js";
-export type { MultiInputDateTimeRangeFieldProps } from './MultiInputDateTimeRangeField';
-export { multiInputDateTimeRangeFieldClasses, getMultiInputDateTimeRangeFieldUtilityClass } from "./multiInputDateTimeRangeFieldClasses.js";
-export type { MultiInputDateTimeRangeFieldClassKey, MultiInputDateTimeRangeFieldClasses } from './multiInputDateTimeRangeFieldClasses';
-export type { MultiInputRangeFieldSlots as MultiInputDateTimeRangeFieldSlots, MultiInputRangeFieldSlotProps as MultiInputDateTimeRangeFieldSlotProps } from '../internals/utils/createMultiInputRangeField';

package/modern/MultiInputDateTimeRangeField/index.js

@@ -1,2 +0,0 @@
-export { MultiInputDateTimeRangeField } from "./MultiInputDateTimeRangeField.js";
-export { multiInputDateTimeRangeFieldClasses, getMultiInputDateTimeRangeFieldUtilityClass } from "./multiInputDateTimeRangeFieldClasses.js";

package/modern/MultiInputDateTimeRangeField/multiInputDateTimeRangeFieldClasses.d.ts

@@ -1,5 +0,0 @@
-import { MultiInputRangeFieldClasses } from "../internals/utils/createMultiInputRangeField/index.js";
-export interface MultiInputDateTimeRangeFieldClasses extends MultiInputRangeFieldClasses {}
-export type MultiInputDateTimeRangeFieldClassKey = keyof MultiInputRangeFieldClasses;
-export declare const multiInputDateTimeRangeFieldClasses: MultiInputRangeFieldClasses;
-export declare const getMultiInputDateTimeRangeFieldUtilityClass: (slot: string) => string;

package/modern/MultiInputDateTimeRangeField/multiInputDateTimeRangeFieldClasses.js

@@ -1,4 +0,0 @@
-import generateUtilityClass from '@mui/utils/generateUtilityClass';
-import generateUtilityClasses from '@mui/utils/generateUtilityClasses';
-export const multiInputDateTimeRangeFieldClasses = generateUtilityClasses('MuiMultiInputDateTimeRangeField', ['root', 'separator']);
-export const getMultiInputDateTimeRangeFieldUtilityClass = slot => generateUtilityClass('MuiMultiInputDateTimeRangeField', slot);

package/modern/MultiInputTimeRangeField/MultiInputTimeRangeField.d.ts

@@ -1,25 +0,0 @@
-import * as React from 'react';
-import { UseTimeRangeManagerReturnValue } from "../managers/index.js";
-import { MultiInputRangeFieldProps } from "../internals/utils/createMultiInputRangeField/index.js";
-import { MultiInputTimeRangeFieldClasses } from "./multiInputTimeRangeFieldClasses.js";
-export interface MultiInputTimeRangeFieldProps<TEnableAccessibleFieldDOMStructure extends boolean> extends MultiInputRangeFieldProps<UseTimeRangeManagerReturnValue<TEnableAccessibleFieldDOMStructure>> {
-  /**
-   * Override or extend the styles applied to the component.
-   */
-  classes?: Partial<MultiInputTimeRangeFieldClasses>;
-}
-type MultiInputTimeRangeFieldComponent = (<TEnableAccessibleFieldDOMStructure extends boolean = true>(props: MultiInputTimeRangeFieldProps<TEnableAccessibleFieldDOMStructure> & React.RefAttributes<HTMLDivElement>) => React.JSX.Element) & {
-  propTypes?: any;
-};
-/**
- * Demos:
- *
- * - [TimeRangeField](http://mui.com/x/react-date-pickers/time-range-field/)
- * - [Fields](https://mui.com/x/react-date-pickers/fields/)
- *
- * API:
- *
- * - [MultiInputTimeRangeField API](https://mui.com/x/api/multi-input-time-range-field/)
- */
-declare const MultiInputTimeRangeField: MultiInputTimeRangeFieldComponent;
-export { MultiInputTimeRangeField };

package/modern/MultiInputTimeRangeField/MultiInputTimeRangeField.js

@@ -1,228 +0,0 @@
-'use client';
-
-import PropTypes from 'prop-types';
-import { useTimeRangeManager } from "../managers/index.js";
-import {
-// The alias is needed to have the doc gen working.
-createMultiInputRangeField as createMultiInputTimeRangeField } from "../internals/utils/createMultiInputRangeField/index.js";
-import { getMultiInputTimeRangeFieldUtilityClass } from "./multiInputTimeRangeFieldClasses.js";
-/**
- * Demos:
- *
- * - [TimeRangeField](http://mui.com/x/react-date-pickers/time-range-field/)
- * - [Fields](https://mui.com/x/react-date-pickers/fields/)
- *
- * API:
- *
- * - [MultiInputTimeRangeField API](https://mui.com/x/api/multi-input-time-range-field/)
- */
-const MultiInputTimeRangeField = createMultiInputTimeRangeField({
-  name: 'MuiMultiInputTimeRangeField',
-  getUtilityClass: getMultiInputTimeRangeFieldUtilityClass,
-  useManager: useTimeRangeManager,
-  allowTriggerShifting: true
-});
-MultiInputTimeRangeField.propTypes = {
-  // ----------------------------- Warning --------------------------------
-  // | These PropTypes are generated from the TypeScript type definitions |
-  // | To update them edit the TypeScript types and run "pnpm proptypes"  |
-  // ----------------------------------------------------------------------
-  /**
-   * 12h/24h view for hour selection clock.
-   * @default utils.is12HourCycleInCurrentLocale()
-   */
-  ampm: PropTypes.bool,
-  /**
-   * If `true`, the `input` element is focused during the first mount.
-   * @default false
-   */
-  autoFocus: PropTypes.bool,
-  /**
-   * Override or extend the styles applied to the component.
-   */
-  classes: PropTypes.object,
-  className: PropTypes.string,
-  component: PropTypes.elementType,
-  /**
-   * String displayed between the start and the end dates.
-   * @default "–"
-   */
-  dateSeparator: PropTypes.string,
-  /**
-   * The default value. Use when the component is not controlled.
-   */
-  defaultValue: PropTypes.arrayOf(PropTypes.object),
-  /**
-   * Defines the `flex-direction` style property.
-   * It is applied for all screen sizes.
-   * @default 'column'
-   */
-  direction: PropTypes.oneOfType([PropTypes.oneOf(['column-reverse', 'column', 'row-reverse', 'row']), PropTypes.arrayOf(PropTypes.oneOf(['column-reverse', 'column', 'row-reverse', 'row'])), PropTypes.object]),
-  /**
-   * If `true`, the component is disabled.
-   * When disabled, the value cannot be changed and no interaction is possible.
-   * @default false
-   */
-  disabled: PropTypes.bool,
-  /**
-   * If `true`, disable values after the current date for date components, time for time components and both for date time components.
-   * @default false
-   */
-  disableFuture: PropTypes.bool,
-  /**
-   * Do not ignore date part when validating min/max time.
-   * @default false
-   */
-  disableIgnoringDatePartForTimeValidation: PropTypes.bool,
-  /**
-   * If `true`, disable values before the current date for date components, time for time components and both for date time components.
-   * @default false
-   */
-  disablePast: PropTypes.bool,
-  /**
-   * Add an element between each child.
-   */
-  divider: PropTypes.node,
-  /**
-   * @default true
-   */
-  enableAccessibleFieldDOMStructure: PropTypes.bool,
-  /**
-   * Format of the date when rendered in the input(s).
-   */
-  format: PropTypes.string,
-  /**
-   * Density of the format when rendered in the input.
-   * Setting `formatDensity` to `"spacious"` will add a space before and after each `/`, `-` and `.` character.
-   * @default "dense"
-   */
-  formatDensity: PropTypes.oneOf(['dense', 'spacious']),
-  /**
-   * Maximal selectable time.
-   * The date part of the object will be ignored unless `props.disableIgnoringDatePartForTimeValidation === true`.
-   */
-  maxTime: PropTypes.object,
-  /**
-   * Minimal selectable time.
-   * The date part of the object will be ignored unless `props.disableIgnoringDatePartForTimeValidation === true`.
-   */
-  minTime: PropTypes.object,
-  /**
-   * Step over minutes.
-   * @default 1
-   */
-  minutesStep: PropTypes.number,
-  /**
-   * Callback fired when the value changes.
-   * @template TValue The value type. It will be the same type as `value` or `null`. It can be in `[start, end]` format in case of range value.
-   * @template TError The validation error type. It will be either `string` or a `null`. It can be in `[start, end]` format in case of range value.
-   * @param {TValue} value The new value.
-   * @param {FieldChangeHandlerContext<TError>} context The context containing the validation result of the current value.
-   */
-  onChange: PropTypes.func,
-  /**
-   * Callback fired when the error associated with the current value changes.
-   * When a validation error is detected, the `error` parameter contains a non-null value.
-   * This can be used to render an appropriate form error.
-   * @template TError The validation error type. It will be either `string` or a `null`. It can be in `[start, end]` format in case of range value.
-   * @template TValue The value type. It will be the same type as `value` or `null`. It can be in `[start, end]` format in case of range value.
-   * @param {TError} error The reason why the current value is not valid.
-   * @param {TValue} value The value associated with the error.
-   */
-  onError: PropTypes.func,
-  /**
-   * Callback fired when the selected sections change.
-   * @param {FieldSelectedSections} newValue The new selected sections.
-   */
-  onSelectedSectionsChange: PropTypes.func,
-  /**
-   * If `true`, the component is read-only.
-   * When read-only, the value cannot be changed but the user can interact with the interface.
-   * @default false
-   */
-  readOnly: PropTypes.bool,
-  /**
-   * The date used to generate a part of the new value that is not present in the format when both `value` and `defaultValue` are empty.
-   * For example, on time fields it will be used to determine the date to set.
-   * @default The closest valid date using the validation props, except callbacks such as `shouldDisableDate`. Value is rounded to the most granular section used.
-   */
-  referenceDate: PropTypes.object,
-  /**
-   * The currently selected sections.
-   * This prop accepts four formats:
-   * 1. If a number is provided, the section at this index will be selected.
-   * 2. If a string of type `FieldSectionType` is provided, the first section with that name will be selected.
-   * 3. If `"all"` is provided, all the sections will be selected.
-   * 4. If `null` is provided, no section will be selected.
-   * If not provided, the selected sections will be handled internally.
-   */
-  selectedSections: PropTypes.oneOfType([PropTypes.oneOf(['all', 'day', 'empty', 'hours', 'meridiem', 'minutes', 'month', 'seconds', 'weekDay', 'year']), PropTypes.number]),
-  /**
-   * Disable specific time.
-   * @param {PickerValidDate} value The value to check.
-   * @param {TimeView} view The clock type of the timeValue.
-   * @returns {boolean} If `true` the time will be disabled.
-   */
-  shouldDisableTime: PropTypes.func,
-  /**
-   * If `true`, the format will respect the leading zeroes (for example on dayjs, the format `M/D/YYYY` will render `8/16/2018`)
-   * If `false`, the format will always add leading zeroes (for example on dayjs, the format `M/D/YYYY` will render `08/16/2018`)
-   *
-   * Warning n°1: Luxon is not able to respect the leading zeroes when using macro tokens (for example "DD"), so `shouldRespectLeadingZeros={true}` might lead to inconsistencies when using `AdapterLuxon`.
-   *
-   * Warning n°2: When `shouldRespectLeadingZeros={true}`, the field will add an invisible character on the sections containing a single digit to make sure `onChange` is fired.
-   * If you need to get the clean value from the input, you can remove this character using `input.value.replace(/\u200e/g, '')`.
-   *
-   * Warning n°3: When used in strict mode, dayjs and moment require to respect the leading zeros.
-   * This mean that when using `shouldRespectLeadingZeros={false}`, if you retrieve the value directly from the input (not listening to `onChange`) and your format contains tokens without leading zeros, the value will not be parsed by your library.
-   *
-   * @default false
-   */
-  shouldRespectLeadingZeros: PropTypes.bool,
-  /**
-   * The props used for each component slot.
-   * @default {}
-   */
-  slotProps: PropTypes.object,
-  /**
-   * Overridable component slots.
-   * @default {}
-   */
-  slots: PropTypes.object,
-  /**
-   * Defines the space between immediate children.
-   * @default 0
-   */
-  spacing: PropTypes.oneOfType([PropTypes.arrayOf(PropTypes.oneOfType([PropTypes.number, PropTypes.string])), PropTypes.number, PropTypes.object, PropTypes.string]),
-  style: PropTypes.object,
-  /**
-   * The system prop, which allows defining system overrides as well as additional CSS styles.
-   */
-  sx: PropTypes.oneOfType([PropTypes.arrayOf(PropTypes.oneOfType([PropTypes.func, PropTypes.object, PropTypes.bool])), PropTypes.func, PropTypes.object]),
-  /**
-   * Choose which timezone to use for the value.
-   * Example: "default", "system", "UTC", "America/New_York".
-   * If you pass values from other timezones to some props, they will be converted to this timezone before being used.
-   * @see See the {@link https://mui.com/x/react-date-pickers/timezone/ timezones documentation} for more details.
-   * @default The timezone of the `value` or `defaultValue` prop is defined, 'default' otherwise.
-   */
-  timezone: PropTypes.string,
-  unstableEndFieldRef: PropTypes.oneOfType([PropTypes.func, PropTypes.object]),
-  unstableStartFieldRef: PropTypes.oneOfType([PropTypes.func, PropTypes.object]),
-  /**
-   * If `true`, the CSS flexbox `gap` is used instead of applying `margin` to children.
-   *
-   * While CSS `gap` removes the [known limitations](https://mui.com/joy-ui/react-stack/#limitations),
-   * it is not fully supported in some browsers. We recommend checking https://caniuse.com/?search=flex%20gap before using this flag.
-   *
-   * To enable this flag globally, follow the [theme's default props](https://mui.com/material-ui/customization/theme-components/#default-props) configuration.
-   * @default false
-   */
-  useFlexGap: PropTypes.bool,
-  /**
-   * The selected value.
-   * Used when the component is controlled.
-   */
-  value: PropTypes.arrayOf(PropTypes.object)
-};
-export { MultiInputTimeRangeField };

package/modern/MultiInputTimeRangeField/index.d.ts

@@ -1,5 +0,0 @@
-export { MultiInputTimeRangeField } from "./MultiInputTimeRangeField.js";
-export type { MultiInputTimeRangeFieldProps } from './MultiInputTimeRangeField';
-export { multiInputTimeRangeFieldClasses, getMultiInputTimeRangeFieldUtilityClass } from "./multiInputTimeRangeFieldClasses.js";
-export type { MultiInputTimeRangeFieldClassKey, MultiInputTimeRangeFieldClasses } from './multiInputTimeRangeFieldClasses';
-export type { MultiInputRangeFieldSlots as MultiInputTimeRangeFieldSlots, MultiInputRangeFieldSlotProps as MultiInputTimeRangeFieldSlotProps } from '../internals/utils/createMultiInputRangeField';

package/modern/MultiInputTimeRangeField/index.js

@@ -1,2 +0,0 @@
-export { MultiInputTimeRangeField } from "./MultiInputTimeRangeField.js";
-export { multiInputTimeRangeFieldClasses, getMultiInputTimeRangeFieldUtilityClass } from "./multiInputTimeRangeFieldClasses.js";

package/modern/MultiInputTimeRangeField/multiInputTimeRangeFieldClasses.d.ts

@@ -1,5 +0,0 @@
-import { MultiInputRangeFieldClasses } from "../internals/utils/createMultiInputRangeField/index.js";
-export interface MultiInputTimeRangeFieldClasses extends MultiInputRangeFieldClasses {}
-export type MultiInputTimeRangeFieldClassKey = keyof MultiInputRangeFieldClasses;
-export declare const multiInputTimeRangeFieldClasses: MultiInputRangeFieldClasses;
-export declare const getMultiInputTimeRangeFieldUtilityClass: (slot: string) => string;

package/modern/MultiInputTimeRangeField/multiInputTimeRangeFieldClasses.js

@@ -1,4 +0,0 @@
-import generateUtilityClass from '@mui/utils/generateUtilityClass';
-import generateUtilityClasses from '@mui/utils/generateUtilityClasses';
-export const multiInputTimeRangeFieldClasses = generateUtilityClasses('MuiMultiInputTimeRangeField', ['root', 'separator']);
-export const getMultiInputTimeRangeFieldUtilityClass = slot => generateUtilityClass('MuiMultiInputTimeRangeField', slot);

package/modern/PickersRangeCalendarHeader/PickersRangeCalendarHeader.d.ts

@@ -1,7 +0,0 @@
-import * as React from 'react';
-import { PickersRangeCalendarHeaderProps } from "./PickersRangeCalendarHeader.types.js";
-type PickersRangeCalendarHeaderComponent = ((props: PickersRangeCalendarHeaderProps & React.RefAttributes<HTMLDivElement>) => React.JSX.Element) & {
-  propTypes?: any;
-};
-declare const PickersRangeCalendarHeader: PickersRangeCalendarHeaderComponent;
-export { PickersRangeCalendarHeader };