Docgen: Errors on TS components whose names are keywords
See original GitHub issueIt appears that a change introduced in 6.0.0-beta.24
is causing my storybook to fail to load:
I’m not sure exactly what is going on here because source maps don’t seem to be working.
Issue Analytics
- State:
- Created 3 years ago
- Comments:17 (4 by maintainers)
Top Results From Across the Web
Troubleshooting - Nintex help documentation
See the errors listed below to see how to troubleshoot them. You'll find the error codes in the error message that Nintex Drawloop...
Read more >@component-controls/react-docgen-info - npm
Start using @component-controls/react-docgen-info in your project by running `npm i ... By default, a return statement at the top level raises an error....
Read more >C Coding Standard
Parens () with Key Words and Functions Policy. Do not put parens next to keywords. Put a space between. Do put parens next...
Read more >OpenFOAM User Guide, Version 10
cluded in its entirety in unmodified form along with one or more other ... The blocks are specified in a list under the...
Read more >R Packages (2e) - 17 Function documentation
17.7.3 Child documents · The name “roxygen” is a nod to the Doxygen documentation generator, which inspired the development of an R package...
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
This seems to happen in cases where a static property is assigned to a component which is exported at its declaration site, e.g.
A workaround seems to be separating the export from the declaration:
Class components with static properties suffer from the same problem:
and the workaround is the same:
I also experience this when my 'default.[exported-component]` is not understood by Storybook, which should be consider as unacceptable because the way I write code should not be affected by how a document-purpose framework works.