All Versions
90
Latest Version
Avg Release Cycle
-
Latest Release
-

Changelog History
Page 6

  • v5.0.0-alpha.5 Changes

    πŸ’₯ Breaking changes
    • [pickers] Restructure props in MonthPicker / YearPicker and DayPicker (#4814) @flaviendelangle

    The props of MonthPicker / YearPicker and DayPicker have been reworked to make them more consistent for a standalone usage (#4814) @flaviendelangle

    MonthPicker: The prop onMonthChange has been removed, you can use onChange instead since every change is a month change

    YearPicker: The prop onYearPicker has been removed, you can use onChange instead since every change is a year change

    DayPicker: The prop isDateDisabled has been removed, you can now use the same validation props as for the other components (maxDate, minDate, shouldDisableDate, disableFuture and disablePast)

    πŸ”„ Changes
    • 🌐 [pickers] Add German (de-DE) translations (#4974) @felixh10r
    • πŸ‘ [pickers] Support action bar on static pickers and improve typing (#5015) @flaviendelangle
  • v5.0.0-alpha.4 Changes

    πŸ’₯ Breaking changes
    • 🚚 The props related to the action bar buttons have been removed (clearable, showTodayButton, cancelText, okText)

    To decide which button must be displayed and in which order, you can now use the actions prop of the actionBar component slot props.

       <DatePicker
         componentsProps={{ 
           actionBar: { 
             // The actions will be the same between desktop and mobile
             actions: ['clear'],
    
             // The actions will be different between desktop and mobile
             actions: (variant) => variant === 'desktop' ? [] : ['clear'],
           }
         }}
       />
    

    The build-in ActionBar component supports 4 different actions: 'clear', 'cancel', 'accept', and 'today'. By default, the pickers will render the cancel and accept button on mobile and no action on desktop.

    If you need other actions, you can provide your own component to the ActionBar component slot

       <DatePicker
         components={{ ActionBar: CustomActionBar }}
       />
    
    πŸ”„ Changes
    • [DatePicker] Fix keyboard accessibility for first and last year (#4807) @alexfauquette
    • [pickers] Add component slot for action bar (#4778) @alexfauquette
    • πŸ‘ [pickers] Add l10n support (#4517) @alexfauquette
    • [pickers] Close Popper when pressing Esc inside a modal (#4499) @alexfauquette
    • πŸ‘ [pickers] Support class slots on toolbar components (#4855) @flaviendelangle
    • [TimePicker] Fix time validation when current date is null (#4867) @flaviendelangle
  • v5.0.0-alpha.3 Changes

    πŸ’₯ Breaking changes
    • Rework the auto-closing behavior of the pickers (#4408) @flaviendelangle

    The disableCloseOnSelect prop has been replaced by a new closeOnSelect prop which has the opposite behavior. The default behavior remains the same (close after the last step on desktop but not on mobile).

       // If you don't want to close after the last step
      -<DatePicker disableCloseOnSelect={false} />
      +<DatePicker closeOnSelect />
    
       // If you want to close after the last step
      -<DatePicker disableCloseOnSelect />
      +<DatePicker closeOnSelect={false} />
    
    πŸ”„ Changes
    • [DatePicker] Ignore Escape when the picker is already closed (#4770) @mikewolfd
    • [DatePicker] Make month year order changeable in header (#4695) @gky360
    • [DateRangePicker] Open view on click, Enter or Space instead of focus (#4747) @alexfauquette
    • πŸ”¨ [DateRangePicker] Refactor tests (#4745) @flaviendelangle
    • 🚚 [DateRangePicker] Remove orientation prop (#4665) @m4theushw
    • 0️⃣ [DateTimePicker] Toolbar should be visible by default on mobile (#4833) @flaviendelangle
    • [MonthPicker] New prop shouldDisableMonth (#4708) @someone635
    • [TimePicker] Disable and invalidate date with minutes not matching minutesStep (#4726) @flaviendelangle
    • πŸ”€ [TimePicker] Don't merge with previous value when new value is not valid (#4847) @flaviendelangle
    • πŸ”¨ [TimePicker] Refactor isTimeDisabled method (#4688) @flaviendelangle
    • [pickers] Add details in invalid mask error (#4501) @alexfauquette
    • [pickers] Add explicit interfaces for components slots and components slots props (#4589) @flaviendelangle
    • [pickers] Add missing peerDependencies for yarn pnp users (#4763) @nate-summercook
    • [pickers] Add overrides to PickersArrowSwitcher (#4672) @m4theushw
    • 🚚 [pickers] Clean component interfaces and remove non-implemented props (#4758) @flaviendelangle
    • [pickers] Do not apply the current time when no date provided in DayPicker (#4649) @flaviendelangle
    • [pickers] Document and refacto the value manager (#4701) @flaviendelangle
    • [pickers] Drop allowSameDateSelection prop (#4808) @flaviendelangle
    • 0️⃣ [pickers] Enable mask by default when using ampm=true (#4731) @alexfauquette
    • [pickers] Fix disabled and readOnly behavior on calendar and clock (#4645) @alexfauquette
    • [pickers] Invalid character does not delete last digit (#4839) @alexfauquette
    • πŸ“œ [pickers] Rename prop date into parsedValue when it can contain a range (#4736) @flaviendelangle
    • [pickers] Rework TDate, TInputDate, TValue and TInputValue generics (#4617) @flaviendelangle
    • [pickers] Rework the date lifecycle in usePickerState (#4408) @flaviendelangle
  • v5.0.0-alpha.2 Changes

    • [pickers] Pass PaperProps to DesktopWrapper component (#4584) @alexfauquette
    • [TimePicker] Fix bug when time picker clear value (#4582) @alexfauquette
    • [DateRangePicker] Fix missing clearable and clearText props (#4511) @zigang93
  • v5.0.0-alpha.1 Changes

    • [ClockPicker] Should call shouldDisableTime with the hours with meridiem (#4404) @flaviendelangle
    • [MonthPicker] Clicking on a PickersMonth button should not trigger the form submit (#4402) @flaviendelangle
    • ⚑️ [TimePicker] Do not update date when updating input in TimePicker (#4398) @flaviendelangle
    • [pickers] Add react-dom to pickers peer deps to satisfy react-transition-group (#4411) @CarsonF
    • [pickers] Add TDate generic to CalendarOrClockPicker component (#4465) @flaviendelangle
    • 0️⃣ [pickers] Fix default props behavior on all pickers (#4451) @flaviendelangle
    • [pickers] Export MuiPickersAdapterContext (#4367) @flaviendelangle
  • v5.0.0-alpha.0 Changes

    πŸ”„ Changes
    • [DatePicker] Import date-picker components from the lab (#3451) @flaviendelangle
  • v4.0.0 Changes

    Aug 27, 2021

    πŸš€ πŸŽ‰ This is the first stable release of the data grid component πŸŽ‰!

    πŸ“š We have been iterating on the component for 18 months. With the introduction of the row edit feature, many bug fixes, and polishing of the documentation, we believe the component is ready for a stable release.

    πŸš€ The MUI X v4.0.0 release supports MUI Core v4 and has partial support for v5-beta. With the soon-to-be-released v5 version of the core components, we are moving ongoing work to the v5 release line (Core and X). πŸ”§ The support for existing projects on MUI v4 won't be a priority going forward. We encourage you to migrate to MUI Core v5-beta and soon MUI X v5-beta. We don't patch, fix, or alter older versions. Using MUI Core v4 with MUI X v5 might lead to extra bundle size and configuration.

    πŸš€ A big thanks to the 6 contributors who made this release possible. Here are some highlights ✨:

    • πŸš€ Introduce the row editing feature (#2098) @m4theushw
    • ⚑️ Rename the XGrid component to DataGridPro (#2382) @m4theushw

    This should help clarify the products vs. plans separation. MUI X is a product line on its own. It contains MIT and Commercial software. Removing X from the name of the paid components should help remove a possible confusion: the MIT version of X is meant to be valuable enough for developers to use it, without feeling that it's crippled compared to other OSS alternatives. The Pro suffix should help make it clear what's MIT and what's not.

    • πŸ’» ✨ Rename the @material-ui npm scope to @mui (#2341) @oliviertassinari

    This is part of the ongoing rebranding of the project and company. Material-UI is our current official name, however, we are going to change it. It's too long to write, read, and pronounce; and it is too closely associated with Material Design. In the near future, the whole project/company is moving to MUI and https://mui.com/.

    • 🚚 πŸ’‘ The api property was removed from the callback params. To access the API, use the DataGridPro (#2312) @DanailH
  • v4.0.0-alpha.9 Changes

    • [DataGrid] Fix keyboard with multiple grids (#562) @dtassone
    • πŸ‘ [DataGrid] Add touch support on column resize (#537) @danailH
    • πŸ”¨ [DataGrid] Refactor containerSizes in smaller state (#544) @dtassone
    • [DataGrid] Fix display of row count and selected rows on mobile (#508) @oliviertassinari
    • [DataGrid] Apply review from #412 (#515) @oliviertassinari
    • [DataGrid] Avoid paint step (#531) @oliviertassinari
    • πŸ”¨ [DataGrid] Refactor rendering, remove rafUpdate (#532) @Dtassone
    • [DataGrid] Add missing reselect dependency (#534) @dtassone
    • [DataGrid] Raf Timer stored in apiRef (#506) @dtassone
    • πŸ‘ [DataGrid] Fix webpack v5 support (#449) @oliviertassinari
    • [DataGrid] Rework columnReorder to work with the new state management (#505) @danailH
    • 🐎 [DataGrid] Fix performance issues (#501) @dtassone
    • πŸ”¨ [DataGrid] Refactor columns scrolling (#500) @dtassone
    • [DataGrid] Replace require with import (#455) @oliviertassinari
    • βͺ [DataGrid] Restore regression test (#503) @oliviertassinari
    • πŸ”¨ [DataGrid] Refactor state (#412) @dtassone
  • v4.0.0-alpha.8 Changes

    • [DataGrid] Fix header row tabIndex (#478) @DanailH
    • [DataGrid] Reduce dependency on lodash, save 1kB gzipped (#450) @oliviertassinari The DataGrid goes from 28.2 kB gzipped down to 27.3 kB gzipped.
    • [XGrid] Second iteration on resizing logic (#436) @oliviertassinari Fix 8 bugs with the resizing.
  • v4.0.0-alpha.7 Changes

    • πŸ‘ [DataGrid] Add column reorder support (#165) @DanailH
    • [DataGrid] Fix iOS issue when scrolling left (#439) @DanailH
    • [DataGrid] Improve sizing logic (#350) @oliviertassinari
    • ⚠ [DataGrid] Improve warning and docs for layouting (#405) @RobertAron