[Typescript] 3 un-typed exports from @material-ui/core
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 😯
@material-ui/core
exports 3 references that are not available in the typescript definitions:
isString
, isNumber
, and styleFunction
Expected Behavior 🤔
@material-ui/core
should either not export these variables or provide Typescript types for them.
Steps to Reproduce 🕹
See the testExports.ts
file and the console output in this demo: https://codesandbox.io/s/optimistic-wilbur-98lq2
Context 🔦
We are trying to dynamically generate an index.ts
file that re-exports all members of @material-ui/core
, except those which we have defined in our wrapping library. e.g., we want to customize the function of the TextField
elements, so want to override that element with our own export but just re-export most other Material components.
While generating this file, we realized that not all of the actually-exported members of @material-ui/core had types for them.
Your Environment 🌎
Tech | Version |
---|---|
Material-UI | v4.8.3 |
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top GitHub Comments
@JonKrone Do you want to take care of the modules in
styles/transitions.js
😃? (We can handle styleFunction later on)I don’t think that any of the modules of
styles/transitions.js
, asideduration
andeasing
, should be available in the barrel index. I would suggest:I believe these methods were only exported recently with #18306.