When the start parameter is missing, the behabiour is arbitary
It seems that the behaviour of the start parameter being missing is server (or perhaps a specific client) dependent. The specification clearely says that it should be inserted at the column of the original request, but the servers clearly expect either for that column to be the beginning of an identifier or for the client to ignore the spec and request from that position anyway. Reading the VSCode code, we see that the 'word' before the cursor is guessed, and if only if BOTH 'start' AND 'length' are supplied, then they are used to determine where insertion starts, otherwise the current 'word' is used. Unclear what 'word' means in the specific contexts, but we're relying on iskeyword.
This commit is contained in:
parent
3aa949431e
commit
2710ee2bfa
2 changed files with 50 additions and 10 deletions
|
|
@ -1,3 +1,10 @@
|
|||
var msg = 'Hello, world!'
|
||||
|
||||
console.log( "OK stuff happened" )
|
||||
var obj = {
|
||||
test: 'testing',
|
||||
toast: function() {
|
||||
return 'toasty' . this.test;
|
||||
}
|
||||
}
|
||||
|
||||
console.log( "OK stuff happened " + obj.toast() )
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue