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
[WIP] Document components using Docz #1939
Conversation
Can you elaborate ? |
Out the top of my head:
|
Remove Playground
Definitely, we will get so much help with this kind of documentation. In the above example, I got some more clarity. +1 |
TS support with Docz is quite good, and automated Props table works as expected (default export is not required anymore, IProps signature is well parsed, just as Cmpt.defaultProps). You should give another try with newly converted TS components. |
The problem is we already have to migrate all ra-core to TypeScript to be able to migrate components. Wanna give us a hand? |
@fzaninotto why not, I can work on a few files. I'll take a look this week-end 👍 |
After playing with Docz, I don't thing this is the right tool to build a robust documentation. |
This Pr is too old. If we ever generate API doc, we'll give Docz another try. |
Testing Docz for API doc generation.
I'm not convinced that docz is finished. Some of the basic requirements aren't yet met, so I'll put this issue on pause until docz matures a bit.