-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
v4.0.1 #2733
Merged
Merged
v4.0.1 #2733
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,13 +3,45 @@ | |
All notable changes to this project will be documented in this file. | ||
See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. | ||
|
||
## 4.0.1 | ||
|
||
_Sep 29, 2021_ | ||
|
||
This version backports bug fixes and some of the features from the v5.x active release line. | ||
As the development of v5 evolves, newer fixes might not be cherry-picked to the legacy version. | ||
To have access to the latest features it is encouraged to upgrade to MUI X v5 and MUI Core v5. | ||
|
||
Big thanks to the 3 contributors who made this release possible. Here are some highlights ✨: | ||
|
||
- 👁 Allow to disable virtualization with the `disableVirtualization` prop (#2728) @m4theushw | ||
- 🕹 Fix navigation between column headers with rows filtered (#2730) @m4theushw | ||
- 🐞 Fix numeric filter operators not handling '0' correctly (#2732) @flaviendelangle | ||
|
||
### `@mui/[email protected]` / `@mui/[email protected]` | ||
|
||
#### Changes | ||
|
||
- [DataGrid] Add `disableVirtualization` prop (#2728) @m4theushw | ||
- [DataGrid] Fix navigation between column headers with rows filtered (#2730) @m4theushw | ||
- [DataGrid] Fix numeric filter operators not handling '0' correctly (#2732) @flaviendelangle | ||
- [DataGridPro] Only apply `checkboxSelectionVisibleOnly` when pagination is enabled (#2731) @flaviendelangle | ||
|
||
### Docs | ||
|
||
- [docs] Improve SEO ranking (#2467) @oliviertassinari | ||
|
||
### Core | ||
|
||
- [core] Allow to create one logger per Grid instance (#2442) @flaviendelangle | ||
- [core] Update monorepo (#2726) @m4theushw | ||
|
||
## 4.0.0 | ||
|
||
_Aug 27, 2021_ | ||
|
||
🎉 This is the first stable release of the data grid component 🎉! | ||
|
||
We have been iterating on the component for [18 months](https://github.com/mui-org/material-ui-x/commit/705cb0f387b5f3aa056bf40c4183a2342b317447). With the introduction of the [row edit](https://material-ui.com/components/data-grid/editing/#row-editing) feature, many bug fixes, and polishing of the documentation, we believe the component is ready for a stable release. | ||
We have been iterating on the component for [18 months](https://github.com/mui-org/material-ui-x/commit/705cb0f387b5f3aa056bf40c4183a2342b317447). With the introduction of the [row edit](https://material-ui.com/components/data-grid/editing/#row-editing) 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](https://github.com/mui-org/material-ui) 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. | ||
|
@@ -24,9 +56,11 @@ A big thanks to the 6 contributors who made this release possible. Here are some | |
|
||
This should help clarify the products vs. plans separation. [MUI X](https://github.com/mui-org/material-ui-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 | ||
|
||
### `@mui/[email protected]` / `@mui/[email protected]` | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
{ | ||
"version": "4.0.0", | ||
"version": "4.0.1", | ||
"npmClient": "yarn", | ||
"useWorkspaces": true | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
{ | ||
"version": "4.0.0", | ||
"version": "4.0.1", | ||
"private": true, | ||
"scripts": { | ||
"start": "yarn docs:dev", | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Do we need this feature in v4?
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.
I would personally encourage we make this release the last cherry-pick on the MUI X v4 release line, and document how to use MUI X v5 with MUI Core v4. I think that doing an update on MUI X v4 would only make sense if there is a major issue: Chrome regression, Node.js regression, webpack regression, security hole, etc. Basically, use the policy we had for Core v4 when we were working on Core v5.
There are 1-2 years of inertia with software. MUI Core v4 kept growing during all the time we were working on v5, while we were almost not making any changes.
Of course, if developers complain too much, then we would need to revisit.
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.
If MUI X v5 + MUI Core v4 is viable (= if users do not find major issues that we would have missed, like weird style collision) I am 100% in favor of this.
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.
An user asked for it and it was simple to cherry-pick: #1902 (comment)