-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
code.context is an empty object #15
Comments
It’s because it’s typescript. I’d take a pr to add support!
…Sent from my iPhone
On Sep 20, 2019, at 10:15 PM, Charlike Mike Reagent ***@***.***> wrote:
Hey @jonschlinkert :)
The comment's code.context is an empty object when using export default, doesn't matter it is name or arrow function`
/**
* Foobar
*
* @param {string} `commit` a commit message
* @api public
*/
export default foobar(commit: string): Commit {}
/**
* Foobar
*
* @param {string} `commit` a commit message
* @api public
*/
export default (commit: string): Commit => {}
It is working when export function.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Nice! That’s awesome!
…Sent from my iPhone
On Sep 20, 2019, at 11:24 PM, Charlike Mike Reagent ***@***.***> wrote:
It's not. The Foobar 2 example don't have types. But okay, cool :)
So far so good, api docs generation in 50 lines :D Just playing around with PoC to test how the latest parse-commits works. And it's great :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Another example is object methods {
use: () => {},
use() {},
use: foo
} Also, the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey @jonschlinkert :)
The comment's
code.context
is an empty object when usingexport default
, arrow function.The text was updated successfully, but these errors were encountered: