flow-jsdoc
flow-jsdoc copied to clipboard
kegsay
Use JSDoc to represent Flow annotations
The following code causes a crash: ```JavaScript function a() { return ''; // a } export { a }; ``` Where as if you remove the `// a` comment it...
In https://github.com/facebook/flow/issues/5670#issuecomment-436965321 @Kegsay offered to hand over the project. Anybody volunteering? @Kegsay Could you update the README with a link to this issue?
Right now, the transformation isn't applied when using `@arg` to document function parameters. It works with `@param` though.
I know it's in the future enhancement section, but is this still being planned? If not, I may fork and try to add it in myself. I really like this...
Hallo, I think this is a great project. What I miss is a way to integrate it into eslint. I know that I can compile it manually and then pass...
When I try to process an es6 javascript exported function types are not generated from jsdoc. Test project: https://github.com/vpmedia/flow-jsdoc-issues
# Problem Esprima can't parse codes which already have flow type annotations. When we have `foo.js` like this: ```js // @flow /** * @param {string} str */ function foo(str): string...
Seems that object spread doesn't work when converting. ```js // Doesn't work return fetch(url, { ...opts, headers, }) // Works return fetch(url, Object.assign({}, opts, { headers, })) ``` ```shell /XXX/node_modules/flow-jsdoc/app.js:84...
Currently when using static properties for classes there is no way to make flow like them. Ideally a similar transform as is done for `@prop` would be done for `@static`.
