Comments (5)
Looking into it quickly, it's struggling to resolve the defaultProps. At a guess it's the spread and the property, though it could also be a failure to grab the information from the other file.
Line 52 (or something around it) will need to be updated, but if you're looking for the fastest way forward, I'd try some different configurations for this line as well as just checking that removing the defaults resolves the problem you are facing.
from extract-react-types.
So it seems that once I move the default props into the button.js
file, the error goes away - any chance you can point me to where I should look for the bug in the codebase? Happy to work on a fix
from extract-react-types.
Thanks Ben, will keep you posted!
from extract-react-types.
The error comes from line 52, which is in the getPropFromObject function.
It fails because a member property doesn't have a key, and we've assumed all members in objects will have a key. I'm guessing the code at this point is a spread or an unresolved import or something?
It may be a new conditional, or an expansion of the conditional on line 46.
from extract-react-types.
Fixed in version 0.16.1 of extract react types and 0.5.3 of kind2string.
from extract-react-types.
Related Issues (20)
- Prop opt out HOT 1
- Type support checklist ✅
- Error: Missing converter for X
- Idea: Prop type skip
- Default values for props are not always extracted
- Improved support for React.memo & React.forwardRef
- Feat: Add ability to hide props from the docs HOT 1
- Feat: Add support for forwardRef used within memo using TS type inference
- Bug: Missing converter for: [path]
- Feat: Add support for memo wrapped around a component as an assigned variable
- Feat: Add support for typecasted HOCs (i.e. typecasted memo'd components)
- Feat: Add a way to display types that are not props
- Issues getting this to work HOT 6
- Support for both React.FC and FC
- PropsTable layout does not show if a prop is required
- Decouple from atlaskit website build HOT 3
- Avoid including `ts-ignore` and `eslint-disable-next-line` in docs HOT 1
- Props not being extracted when using both memo and forward ref HOT 1
- Babel plugin fails to extract props when project Babel config contains overrides
- Can't extract types from namespace type.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from extract-react-types.