-
Notifications
You must be signed in to change notification settings - Fork 485
No support for exported flow types #359
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
Comments
It seems to me like this is a more general issue, in fact. Using the I set up a small demo demonstrating this: |
Thanks for the testcase @ajhyndman. Going to look into a cause for this. |
Okay, so in the case of: /**
* Return a number multiplied by two.
* @memberof main
* @param a A number to be doubled
* @returns The input number, doubled
*/
function double (a: number): number {
// Do some stuff
return a * 2;
} This is that right now we intelligently let you specify That said, this is a different issue than the OP, since this happens on the code irregardless of the |
In current master/beta15, this bug persists: the output for the given example is # SomeObjectAPI
Define my object API Will have to look into this: I think the issue is that the template doesn't output the type of typedefs. |
Now compatible with 13.x
When splitting and reusing types between multiple modules, it's common to use Flow's
export type
syntax.This doesn't seem to be actually documented but it's explained in this blog post: http://flowtype.org/blog/2015/02/18/Import-Types.html
Right now, documentation.js seems to only infer the name from these kinds of declarations. So if you have something like:
the generated documentation only shows something like:
However, if I were to do something like
it would work fine.
The text was updated successfully, but these errors were encountered: