Comments (4)
I assume that whatever renders the docs is not set up to render unions. The output from react-docgen should be something like
"transform": {
"type": {
"name": "arrayOf",
"value": {
"name": "union",
"value": [
{
"name": "shape",
"value": {
"rotation": {
"name": "number"
}
}
},
{
"name": "shape",
"value": {
"scaleX": {
"name": "number"
}
}
},
{
"name": "shape",
"value": {
"scaleY": {
"name": "number"
}
}
},
{
"name": "shape",
"value": {
"translateX": {
"name": "number"
}
}
},
{
"name": "shape",
"value": {
"translateY": {
"name": "number"
}
}
}
]
}
},
"required": false,
"description": ""
}
}
So all you have to do is iterate over value
and build the output you want.
from react-docgen.
Thanks! Fixed here: facebook/react-native#1181
from react-docgen.
Awesome!
from react-docgen.
I'm using styleguidist which uses react-docgen, but it still outputs "union" for Flow types such as ("foo" | "bar"). Is there a plugin or patch or something to make it list the union types?
I realize this in an old thread, but if there is an answer, I assume it would be useful to others.
from react-docgen.
Related Issues (20)
- react-docgen cannot extract comments with hermes-parser HOT 3
- Fow indexed access types results in `unknow` HOT 2
- useCallback + useImperativeHandle methods
- Expose more TypeScript types HOT 1
- react-docgen v6.0.0 & older changelogs HOT 2
- Property accessors as template literals causes errors with react-docgen v7 HOT 4
- Better TS enum support
- TS forwardRef support HOT 1
- With Typescript Omit Union types get lost
- With forwardRef Union types get lost HOT 1
- Internal server error: Argument must be Identifier, Literal, QualifiedTypeIdentifier or TSQualifiedName. Received 'TemplateLiteral' HOT 2
- Fails when a namespaced export is used HOT 1
- When postcss modules are present, in some scenarios react-docgen tries to parse css files HOT 2
- Typescript: Component props not parsed with 'call signature' type
- Typescript: Component declaration reference is not recognized by parser
- @defaultValue is not parsed from interface
- "Attempted to resolveName for an unsupported path" error HOT 2
- Decorators must be placed *after* the 'export' keyword. Remove the 'decoratorsBeforeExport: false' option to use the '@decorator export class {}' syntax.
- Using `Readonly<T>` utility type results in losing pieces of `T`'s information
- TypeScript: Missing Union Elements of Indexed Access 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 react-docgen.