-
-
Notifications
You must be signed in to change notification settings - Fork 81
[BugFix] Incorrect behavior when arrow functions are used as default values #189
Conversation
f0a58a5
to
3e7b614
Compare
3e7b614
to
f052fe0
Compare
Can this be reviewed by someone ? |
Can someone look into this ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me. Thanks! Sorry this has slipped through the cracks-- most of the Doctrine folks on the core ESLint team have been unavailable lately.
I see. Thanks for reviewing. |
@eslint/eslint-team Can someone else review this? I'm happy to merge if we can get one more set of eyes on this. |
@lorefnon Sorry about the delay on this! There isn't a lot of traffic in this repo and it's easy to miss things. Thanks for the contribution! |
Merged, thanks @lorefnon for contributing! (And thanks very much for your patience!) |
Glad to see this merged. |
Can you please release this ? |
When arrow functions are used as default values in arguments, the output is currently incorrect.
Example:
Expected default value in generated documentation:
() => {}
Current default value in generated documentation:
()