-
Notifications
You must be signed in to change notification settings - Fork 12.9k
Signature help turns off current-parameter display for non-trailing rest parameters #42592
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
Merged
sandersn
merged 7 commits into
master
from
signature-help-support-non-trailing-variadic-parameters
Feb 5, 2021
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
1cf9a73
Signature help: support non-trailing rest parameters
sandersn e55212e
Change 'variadic' to 'rest'
sandersn 692c590
fix missed rename
sandersn f0896f3
use single, original tuple instead
sandersn 3351ccb
Revert "use single, original tuple instead"
sandersn 2e32638
Improve sig help of trailing rest too
sandersn 88e83d1
update API baselines
sandersn File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
/// <reference path='fourslash.ts' /> | ||
|
||
////export function leading(...args: [...names: string[], allCaps: boolean]): void { | ||
////} | ||
//// | ||
////leading(/*1*/); | ||
////leading("ok", /*2*/); | ||
////leading("ok", "ok", /*3*/); | ||
|
||
verify.signatureHelp( | ||
{ | ||
marker: "1", | ||
text: "leading(...names: string[], allCaps: boolean): void", | ||
overloadsCount: 1, | ||
parameterCount: 2, | ||
isVariadic: true, | ||
}, | ||
{ | ||
marker: "2", | ||
text: "leading(...names: string[], allCaps: boolean): void", | ||
overloadsCount: 1, | ||
parameterCount: 2, | ||
isVariadic: true, | ||
}, | ||
{ | ||
marker: "3", | ||
text: "leading(...names: string[], allCaps: boolean): void", | ||
overloadsCount: 1, | ||
parameterCount: 2, | ||
isVariadic: true, | ||
}, | ||
); |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
/// <reference path='fourslash.ts' /> | ||
|
||
////export function leading(allCaps: boolean, ...names: string[]): void { | ||
////} | ||
//// | ||
////leading(/*1*/); | ||
////leading(false, /*2*/); | ||
////leading(false, "ok", /*3*/); | ||
|
||
verify.signatureHelp( | ||
{ | ||
marker: "1", | ||
text: "leading(allCaps: boolean, ...names: string[]): void", | ||
overloadsCount: 1, | ||
parameterCount: 2, | ||
parameterName: "allCaps", | ||
parameterSpan: "allCaps: boolean", | ||
isVariadic: true, | ||
}, | ||
{ | ||
marker: "2", | ||
text: "leading(allCaps: boolean, ...names: string[]): void", | ||
overloadsCount: 1, | ||
parameterCount: 2, | ||
parameterName: "names", | ||
parameterSpan: "...names: string[]", | ||
isVariadic: true, | ||
}, | ||
{ | ||
marker: "3", | ||
text: "leading(allCaps: boolean, ...names: string[]): void", | ||
overloadsCount: 1, | ||
parameterCount: 2, | ||
parameterName: "names", | ||
parameterSpan: "...names: string[]", | ||
isVariadic: true, | ||
}, | ||
); |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
We could also make this conditional upon
argumentIndex >= firstRest
if we wanted parameter highlighting to work up until the first rest, where the ambiguity begins. But maybe that would be a worse experience than consistently seeing no highlighting. I personally feel like parameter highlighting is pretty useful when parameters have JSDoc description, and it might be worthwhile to show them as often as we can. But it might be pretty confusing for it to stop working halfway through typing call arguments. Don’t have a super strong opinion here.