-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Fixed an out-of-order quick info issue with contextual rest parameter #57580
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -85,7 +85,7 @@ | |
// return curry(getStylingByKeys, 2)(mergedStyling, ...args); | ||
// ^^^^ | ||
// | ---------------------------------------------------------------------- | ||
// | (parameter) args: any | ||
// | (parameter) args: [] | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this is the correct display that we can see when hovering at this location in the playground (after the playgrounds gets typechecked first): TS playground. If we make an edit and quickly hover over this location we can sometimes "catch" this |
||
// | ---------------------------------------------------------------------- | ||
// }, | ||
// 3 | ||
|
@@ -135,8 +135,12 @@ | |
"kind": "space" | ||
}, | ||
{ | ||
"text": "any", | ||
"kind": "keyword" | ||
"text": "[", | ||
"kind": "punctuation" | ||
}, | ||
{ | ||
"text": "]", | ||
"kind": "punctuation" | ||
} | ||
], | ||
"documentation": [] | ||
|
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.
If I'm not mistaken this function wasn't proving that the input is
JSDocPropertyLikeTag
- some extra checks on a variable withJSDocPropertyLikeTag
type were done here and it could still returnfalse
for it. So this wasn't a correct return type annotationThere 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.
It's certainly not the first type guard we've had which has lied for convenience's sake. But it doesn't seem like it really helped here.