-
-
Notifications
You must be signed in to change notification settings - Fork 296
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for function components that return null #924
base: main
Are you sure you want to change the base?
Conversation
|
✅ Deploy Preview for react-docgen ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
const def = parse.statement(` | ||
function Foo (props) { | ||
return null; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What worries me is that literaly any function that returns null will be detected as react component.
Same for the other usecase.
Add support for function components that only return null:
and add support for components that only return a prop (directly, without a fragment):
Fixes #926