-
Notifications
You must be signed in to change notification settings - Fork 12.9k
Open
Labels
Experience EnhancementNoncontroversial enhancementsNoncontroversial enhancementsHelp WantedYou can do thisYou can do thisSuggestionAn idea for TypeScriptAn idea for TypeScript
Milestone
Description
Suggestion
I often find myself describing function params as labeled tuples. A simple example:
type AddArgs = [a: number, b: number];
function add(...[a, b]: AddArgs): number {
return a + b;
}
Unfortunately, this approach prevents us from attaching tsdocs to the params. The following does not work :/
type AddArgs = [a: number, b: number];
/**
* @param a the first number
* @param b the second number
*/
function add(...[a, b]: AddArgs): number {
return a + b;
}
I propose that one be able to attach tsdocs to labeled tuple elements, just as one does to object keys.
type AddArgs = [
/** the first number */
a: number,
/** the second number */
b: number,
];
I also propose that––when spread in place of function params––these tsdocs are treated as if they were the result of @param
annotations on the function declaration.
🔍 Search Terms
Documentation, labeled, tuple, elements, tsdocs, signature
✅ Viability Checklist
My suggestion meets these guidelines:
- This wouldn't be a breaking change in existing TypeScript/JavaScript code
- This wouldn't change the runtime behavior of existing JavaScript code
- This could be implemented without emitting different JS based on the types of the expressions
- This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- This feature would agree with the rest of TypeScript's Design Goals.
tjjfvi and sirius16
Metadata
Metadata
Assignees
Labels
Experience EnhancementNoncontroversial enhancementsNoncontroversial enhancementsHelp WantedYou can do thisYou can do thisSuggestionAn idea for TypeScriptAn idea for TypeScript