-
Notifications
You must be signed in to change notification settings - Fork 534
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
Debug docgen behaviour #1425
Debug docgen behaviour #1425
Conversation
|
size-limit report 📦
|
Agreed. I'm happy to change the way we write components if it also makes our code simpler and easier to reason about 👍 |
I'm not working on this pull request anymore :) |
Chasing #1419
From what I'm noticing in fixtures from react-docgen-typescript, there is a very specific syntax that works for docgen, which we might want to adopt
These are the components that have missing data:
1. forwardRef
2. TextInput
After making the above change, TextInput shows up in docgen output, but not it's props.
Trying to make the smallest reproducible bug, it seems like docgen isn't able to parse this specific line. Still looking for the fix.
How to run this test:
To get the list
To debug syntax:
then keep an eye on
debug/output.json
I don't love the idea of changing how we write code for tooling needs, but because most of these are surface level changes that don't affect readability of the code, I don't mind either 🤷♀️