-
-
Notifications
You must be signed in to change notification settings - Fork 299
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
Nested type descriptions #683
Comments
just would like to add my +1 here, in typescript nested interfaces seem to not be resolved currently. if this is not already supported, I'd request for the output of the E.g. both below cases should yield the same output: case 1. without nested interface
current output (expected output also for case 2.)
VS. case 2. with nested interface
=>
|
When TypeScript support was implemented there was the decision made to handle interfaces different than object types and type aliases. The reason was that interfaces might be documented separately and linked from the component docs. I can see that use case but also think that the same could apply for object types or enums. So it might be nice to find a way to allow this will still documenting everything. What I'm thinking of is to handle interfaces and object types exactly the same, except to somehow make it clear that it is an interface. In addition it might be interesting to add a Maybe something like this for your example above. Would that work for you?
|
This issue with flow and missing descriptions will be fixed in the next release. see #810 |
I don't think this is yet in the latest release ( |
Sorry if this has been reported before in some form before, but is there currently support for nested type descriptions? For example, given the following structure (using Flow and
[email protected]
):^ Does not generate any
description
for the Panel -props. Is this intentional? The output for a Panel is:The text was updated successfully, but these errors were encountered: