-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Added DefinitionAndBoundSpan command #19175
Changes from 14 commits
1cb2d24
c6a8a32
b86153d
8004fec
16c3255
051da11
f8ccde5
ae266f6
7f577dc
c62f288
7fd9fe6
5b7abf2
f3059ce
c4a675e
d5c18a6
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 |
---|---|---|
|
@@ -117,7 +117,7 @@ namespace ts.server { | |
body: undefined | ||
}); | ||
}); | ||
it ("should handle literal types in request", () => { | ||
it("should handle literal types in request", () => { | ||
const configureRequest: protocol.ConfigureRequest = { | ||
command: CommandNames.Configure, | ||
seq: 0, | ||
|
@@ -175,6 +175,8 @@ namespace ts.server { | |
CommandNames.Configure, | ||
CommandNames.Definition, | ||
CommandNames.DefinitionFull, | ||
CommandNames.DefinitionAndBoundSpan, | ||
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. I notice that the regular 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. Offline, I think we established that VS Code will probably not consume the new API. If this API is just for VS, should it have "Full" in the name? I think that's how we usually distinguish. In reply to: 144675978 [](ancestors = 144675978) 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. Based on a discussion with @mhegazy, I have added the method for the simplified, hence, the "full" has been updated. |
||
CommandNames.DefinitionAndBoundSpanFull, | ||
CommandNames.Implementation, | ||
CommandNames.ImplementationFull, | ||
CommandNames.Exit, | ||
|
@@ -341,7 +343,7 @@ namespace ts.server { | |
session.addProtocolHandler(command, () => resp); | ||
|
||
expect(() => session.addProtocolHandler(command, () => resp)) | ||
.to.throw(`Protocol handler already exists for command "${command}"`); | ||
.to.throw(`Protocol handler already exists for command "${command}"`); | ||
}); | ||
}); | ||
|
||
|
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.
It seems like this is actually the name of the API under test. #Closed
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.
Which one is reported when the argument is
undefined
? Does it matter?In reply to: 146340127 [](ancestors = 146340127)
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.
The argument is not going to be undefined only the response from the argument function. It happens when the token doesn't contain a definition.