Closed MaffooBristol closed 4 years ago
Describe the bug In modern JS you can do function foo({ a, b }) {} rather than function foo(args) { args.a }
function foo({ a, b }) {}
function foo(args) { args.a }
However, this extension gets a bit confused and thinks that the braces are arguments.
Code Snippet
function AuthChecker({ dispatch, authed, session }) { }
Output
/** * [AuthChecker description] * * @param {[type]} { * [{ description] * @param {[type]} dispatch * [dispatch description] * @param {[type]} authed * [authed description] * @param {[type]} session * [session description] * @param {[type]} } * [ description]} * * @return {[type]} * [return description] */
Expected
/** * [AuthChecker description] * * @param {[type]} dispatch * [dispatch description] * @param {[type]} authed * [authed description] * @param {[type]} session * [session description] * * @return {[type]} * [return description] */
Environment (please complete the following information):
This will be fixed in the next release.
Describe the bug In modern JS you can do
function foo({ a, b }) {}
rather thanfunction foo(args) { args.a }
However, this extension gets a bit confused and thinks that the braces are arguments.
Code Snippet
Output
Expected
Environment (please complete the following information):