[ListItem] Having styleOverrides key brokes component
See original GitHub issue- The issue is present in the latest release.
- I have searched the issues of this repository and believe that this is not a duplicate.
Current Behavior 😯
I guess global style overrides of ListItem
component is broken.
Instead of correct rendering, it gives this error.
styleProps
is undefined
Expected Behavior 🤔
Should work as expected
Steps to Reproduce 🕹
https://codesandbox.io/s/gallant-jackson-28vmx?file=/src/index.tsx
Steps:
- Have simple List usage code
- Overrides with
styleOverrides
Context 🔦
Interestingly, if I remove <ListItemSecondaryAction />
, the error goes away.
Your Environment 🌎
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
[ListItem] Having styleOverrides key brokes component #25774
The issue is present in the latest release. I have searched the issues of this repository and believe that this is not a...
Read more >how to override material UI .Mui-selected on ListItemButton ...
I have a list item button with a selected ...
Read more >Migration from v4 to v5 - MUI
Handling Breaking Changes; Migrate theme's styleOverrides to emotion ... The theme.palette.text.hint key was unused in MUI components, and has been removed.
Read more >@mui/material | Yarn - Package Manager
React components that implement Google's Material Design. ... MUI Core contains foundational React UI component libraries for shipping new features faster.
Read more >Unity React Components - GitHub Pages
Make the component stretch to all available height like its Material UI counterpart does ... JSS had a major upgrade, which deprecated global...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ifndefdeadmau5 I’ve included the fix in https://github.com/mui-org/material-ui/pull/25777 no need for creating additional PR 😃
@mnajdova We have multiple components with two
overridesResolver
(e.g. Autocomplete, Badge, SpeedDial) that are valid (to workaround different DOM structure), I guess we could do the same?Oh, actually, the multiple
overridesResolver
in Step components are not valid ⚠️