-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[DataGridPro] Avoid proptypes warnings with header filters in React 17 #17482
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
Merged
cherniavskii
merged 2 commits into
mui:master
from
cherniavskii:supress-proptypes-warnings-react-17
Apr 22, 2025
Merged
[DataGridPro] Avoid proptypes warnings with header filters in React 17 #17482
cherniavskii
merged 2 commits into
mui:master
from
cherniavskii:supress-proptypes-warnings-react-17
Apr 22, 2025
Conversation
This file contains hidden or 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
Thanks for adding a type label to the PR! 👍 |
50f21cb
to
07d4fc3
Compare
Deploy preview: https://deploy-preview-17482--material-ui-x.netlify.app/ |
arminmeh
approved these changes
Apr 22, 2025
KenanYusuf
approved these changes
Apr 22, 2025
Cherry-pick PRs will be created targeting branches: v7.x |
bernardobelchior
pushed a commit
to bernardobelchior/mui-x
that referenced
this pull request
Apr 22, 2025
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
core
Covers general upkeep, such as minor refactoring, typo fixes, or structural changes.
dx
Related to developers' experience
feature: Filtering on header
Related to the header filtering (Pro) feature
needs cherry-pick
The PR should be auto-cherry-picked to a version branch after merge—add a version label as target
plan: Pro
Impact at least one Pro user
scope: data grid
Changes or issues related to the data grid product
type: bug
A bug or unintended behavior in the components.
type: enhancement
This is not a bug, nor a new feature
v7.x
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.
Fixes https://mui.zendesk.com/agent/tickets/26834
We use the
useId()
hook to generate IDs for these props.But in React 17,
useId()
returnsundefined
as the initial value, which triggers the propTypes warning:https://github.com/mui/material-ui/blob/e3d807e35a1b410dfb0d5240e72b8a8846768c03/packages/mui-utils/src/useId/useId.ts#L7-L20
Since we're going to remove propTypes anyway, I think it's OK to mark these specific props as optional.