JS Closure Compiler, @param syntax for array destructuring?
I'm unable to find the correct syntax for @param
annotations for array destructuring. E.g.:
let destructArray = ([one, two]) => one + two;
I tried imitating the object destructuring syntax:
// object destructuring works
/** @param {{one: number, two: number}} o */
let destructObject = ({one, two}) => one + two;
// array destructuring does not works
/** @param {[one: number, two: number]} a */
let destructArray = ([one, two]) => one + two;
But that's not valid syntax. I've also tried /** @param {Array<number>} a */
, but then it expects a single parameter named a
, not one
and two
.
Does anyone know the correct syntax to use for array destructuring?
javascript ecmascript-6 google-closure-compiler destructuring
add a comment |
I'm unable to find the correct syntax for @param
annotations for array destructuring. E.g.:
let destructArray = ([one, two]) => one + two;
I tried imitating the object destructuring syntax:
// object destructuring works
/** @param {{one: number, two: number}} o */
let destructObject = ({one, two}) => one + two;
// array destructuring does not works
/** @param {[one: number, two: number]} a */
let destructArray = ([one, two]) => one + two;
But that's not valid syntax. I've also tried /** @param {Array<number>} a */
, but then it expects a single parameter named a
, not one
and two
.
Does anyone know the correct syntax to use for array destructuring?
javascript ecmascript-6 google-closure-compiler destructuring
2
For others who, like me, hoped JSDoc's destructuring support would solve this, it appears not. I answered hoping it would (you can see the answer here: pastebin.com/dNgVLCMd), but the OP said it didn't work. (Thanks for letting me know, junvar, and good luck -- it may be that CC doesn't support this yet.)
– T.J. Crowder
Nov 27 '18 at 17:27
1
Your answer was still helpful in providing background; thank you.
– junvar
Nov 27 '18 at 17:40
add a comment |
I'm unable to find the correct syntax for @param
annotations for array destructuring. E.g.:
let destructArray = ([one, two]) => one + two;
I tried imitating the object destructuring syntax:
// object destructuring works
/** @param {{one: number, two: number}} o */
let destructObject = ({one, two}) => one + two;
// array destructuring does not works
/** @param {[one: number, two: number]} a */
let destructArray = ([one, two]) => one + two;
But that's not valid syntax. I've also tried /** @param {Array<number>} a */
, but then it expects a single parameter named a
, not one
and two
.
Does anyone know the correct syntax to use for array destructuring?
javascript ecmascript-6 google-closure-compiler destructuring
I'm unable to find the correct syntax for @param
annotations for array destructuring. E.g.:
let destructArray = ([one, two]) => one + two;
I tried imitating the object destructuring syntax:
// object destructuring works
/** @param {{one: number, two: number}} o */
let destructObject = ({one, two}) => one + two;
// array destructuring does not works
/** @param {[one: number, two: number]} a */
let destructArray = ([one, two]) => one + two;
But that's not valid syntax. I've also tried /** @param {Array<number>} a */
, but then it expects a single parameter named a
, not one
and two
.
Does anyone know the correct syntax to use for array destructuring?
javascript ecmascript-6 google-closure-compiler destructuring
javascript ecmascript-6 google-closure-compiler destructuring
asked Nov 27 '18 at 16:35
junvarjunvar
479514
479514
2
For others who, like me, hoped JSDoc's destructuring support would solve this, it appears not. I answered hoping it would (you can see the answer here: pastebin.com/dNgVLCMd), but the OP said it didn't work. (Thanks for letting me know, junvar, and good luck -- it may be that CC doesn't support this yet.)
– T.J. Crowder
Nov 27 '18 at 17:27
1
Your answer was still helpful in providing background; thank you.
– junvar
Nov 27 '18 at 17:40
add a comment |
2
For others who, like me, hoped JSDoc's destructuring support would solve this, it appears not. I answered hoping it would (you can see the answer here: pastebin.com/dNgVLCMd), but the OP said it didn't work. (Thanks for letting me know, junvar, and good luck -- it may be that CC doesn't support this yet.)
– T.J. Crowder
Nov 27 '18 at 17:27
1
Your answer was still helpful in providing background; thank you.
– junvar
Nov 27 '18 at 17:40
2
2
For others who, like me, hoped JSDoc's destructuring support would solve this, it appears not. I answered hoping it would (you can see the answer here: pastebin.com/dNgVLCMd), but the OP said it didn't work. (Thanks for letting me know, junvar, and good luck -- it may be that CC doesn't support this yet.)
– T.J. Crowder
Nov 27 '18 at 17:27
For others who, like me, hoped JSDoc's destructuring support would solve this, it appears not. I answered hoping it would (you can see the answer here: pastebin.com/dNgVLCMd), but the OP said it didn't work. (Thanks for letting me know, junvar, and good luck -- it may be that CC doesn't support this yet.)
– T.J. Crowder
Nov 27 '18 at 17:27
1
1
Your answer was still helpful in providing background; thank you.
– junvar
Nov 27 '18 at 17:40
Your answer was still helpful in providing background; thank you.
– junvar
Nov 27 '18 at 17:40
add a comment |
1 Answer
1
active
oldest
votes
Closure Compiler does not currently support different types at different array indexes. So in this case, all you do is:
/** @type {function(!Array<number>):number} */
let destructArray = ([one, two]) => one + two;
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53504192%2fjs-closure-compiler-param-syntax-for-array-destructuring%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Closure Compiler does not currently support different types at different array indexes. So in this case, all you do is:
/** @type {function(!Array<number>):number} */
let destructArray = ([one, two]) => one + two;
add a comment |
Closure Compiler does not currently support different types at different array indexes. So in this case, all you do is:
/** @type {function(!Array<number>):number} */
let destructArray = ([one, two]) => one + two;
add a comment |
Closure Compiler does not currently support different types at different array indexes. So in this case, all you do is:
/** @type {function(!Array<number>):number} */
let destructArray = ([one, two]) => one + two;
Closure Compiler does not currently support different types at different array indexes. So in this case, all you do is:
/** @type {function(!Array<number>):number} */
let destructArray = ([one, two]) => one + two;
answered Nov 27 '18 at 18:07
Chad KillingsworthChad Killingsworth
13.1k22951
13.1k22951
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53504192%2fjs-closure-compiler-param-syntax-for-array-destructuring%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
For others who, like me, hoped JSDoc's destructuring support would solve this, it appears not. I answered hoping it would (you can see the answer here: pastebin.com/dNgVLCMd), but the OP said it didn't work. (Thanks for letting me know, junvar, and good luck -- it may be that CC doesn't support this yet.)
– T.J. Crowder
Nov 27 '18 at 17:27
1
Your answer was still helpful in providing background; thank you.
– junvar
Nov 27 '18 at 17:40