Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Tooltip] TypeScript issue with children type and React.FunctionComponent
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 😯
When creating functional wrapper components in Typescript, I get type errors due to Material-UI expecting a ReactElement<any, any> “children” prop while React provides a ReactNode (due to React.FunctionComponent<Props> wrapping my props into React.PropsWithChildren).
When compiling in strict TS mode, this breaks the build.
In non-strict mode, the error is ignored and the component works well.
Expected Behavior 🤔
Successful compilation.
Steps to Reproduce 🕹
Please check out https://codesandbox.io/s/sad-dubinsky-pdktq?file=/src/Tooltip.tsx
Your Environment 🌎
| Tech | Version |
|---|---|
| Material-UI | v4.11.0 |
| React | v17.0.0 |
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I generally don’t recommend
React.FunctionComponentbecause it injects achildrentype. See https://react-typescript-cheatsheet.netlify.app/docs/basic/getting-started/function_components/ for more information.You’re looking for something like
function Component(props: { children?: React.Element<any, any>}). Hope that helps.They do. You just have to make sure
childrenhas the same type thatTooltip’schildrenhave.