-
-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump MUI X to 7.0.0 (major) #3310
Conversation
a0b278e
to
f835a82
Compare
f835a82
to
2b7ddc2
Compare
Comment to keep track of issues while migrating (not all of these are directly related to the migration):
|
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
@danilo-leal improved the default design in #11529 |
<TreeItem disabled nodeId="::loading::" label={<Skeleton />} /> | ||
<TreeItem disabled nodeId="::loading::" label={<Skeleton />} /> | ||
<TreeItem disabled nodeId="::loading::" label={<Skeleton />} /> | ||
<TreeItem disabled itemId="::loading::" label={<Skeleton />} /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You don't have any issues rendering 3 items with the same ID?
This should crash or at least cause bugs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this code is part of an unreleased part of the ui behind a feature flag. It seems to crash indeed. I added unique ids.
If you don't want to set all the template parameters, I think you can use
Unavoidable, we needed type-safety for our slots for the material-less datagrid. Keeping
You should select for |
This PR contains the following updates:
6.19.8
->7.0.0
6.19.8
->7.0.0
6.19.8
->7.0.0
6.19.8
->7.0.0
6.19.8
->7.0.0
6.17.0
->7.0.0
Release Notes
mui/mui-x (@mui/x-charts)
v7.0.0
Compare Source
Mar 22, 2024
We're excited to announce the first v7 stable release! 🎉🚀
This is now the officially supported major version, where we'll keep rolling out new features, bug fixes, and improvements.
Migration guides are available with a complete list of the breaking changes:
We'd like to offer a big thanks to the 12 contributors who made this release possible. Here are some highlights ✨:
viewRenderers
onDateTimePicker
(#12441) @LukasTydensity
for the Data Grid (#12332) @MBilalShafiData Grid
Breaking changes
The
density
is a controlled prop now, if you were previously passing thedensity
prop to the Data Grid, you will need to do one of the following:initialState.density
to initialize it.onDensityChange
callback to update thedensity
prop accordingly for it to work as expected.The selector
gridDensityValueSelector
was removed, use thegridDensitySelector
instead.The props
rowBuffer
andcolumnBuffer
were renamed torowBufferPx
andcolumnBufferPx
.Their value is now a pixel value rather than a number of items. Their default value is now
150
.The props
rowThreshold
andcolumnThreshold
have been removed.If you had the
rowThreshold
prop set to0
to force new rows to be rendered more often – this is no longer necessary.@mui/[email protected]
ElementType
usage (#12479) @cherniavskiirows
an optional prop (#12478) @MBilalShafi@mui/[email protected]
Same changes as in
@mui/[email protected]
.@mui/[email protected]
Same changes as in
@mui/[email protected]
, plus:Date and Time Pickers
Breaking changes
DesktopDateTimePicker
view rendering has been optimized by using the same technique as forDesktopDateTimeRangePicker
.dateTimeViewRenderers
have been removed in favor of reusing existing time view renderers (renderTimeViewClock
,renderDigitalClockTimeView
andrenderMultiSectionDigitalClockTimeView
) and date view renderer (renderDateViewCalendar
).renderTimeViewClock
to time view renderers will no longer revert to the old behavior of rendering only date or time view.@mui/[email protected]
DesktopDateTimePicker
(#12441) @LukasTy@mui/[email protected]
Same changes as in
@mui/[email protected]
, plus:JSDoc
(#12518) @LukasTyCharts
@mui/[email protected]
CartesianContextProvider
(#12461) @JanpotTree View
Breaking changes
nodeId
prop used by theTreeItem
has been renamed toitemId
for consistency:The focus is now applied to the Tree Item root element instead of the Tree View root element.
This change will allow new features that require the focus to be on the Tree Item,
like the drag and drop reordering of items.
It also solves several issues with focus management,
like the inability to scroll to the focused item when a lot of items are rendered.
This will mostly impact how you write tests to interact with the Tree View:
For example, if you were writing a test with
react-testing-library
, here is what the changes could look like:@mui/[email protected]
nodeId
toitemId
(#12418) @noraleonteContentComponent
prop to avoid using the word "node" (#12476) @flaviendelangle@mui/[email protected]
Docs
Core
@mui/material
peer dependency for all packages (#12516) @LukasTyno-restricted-imports
ESLint rule not working for Data Grid packages (#12477) @cherniavskiino-response
action runs (#12491) @michaldudaklegacy
browserlistrc
entry (#12415) @LukasTyConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.