Closed joneugster closed 1 week ago
You're comparing the implementation details with the interface. There is no supposed difference as the exact same code is used in both places.
Are you encountering any issue?
Hmm, I am experiencing issues, but I think that was a complete misjudgment, and had nothing to do with the _character
.
I don't think I can minimalise this easily, but I know have a code-snippet that looks like this:
range: {
// start: selection.start, // This fails...
// end: selection.end,
start: {line: selection.start.line, character: selection.start.character}, // this succeeds... `selection.start._character` also suceeded
end: {line: selection.end.line, character: selection.end.character}
},
I don't understand why the latter works, but I don't think it has anything to do with this package.
Sorry for the noise and thanks for the fast answer!
I'm sorry if this is a dumb question and I don't fully understand what I'm doing.
But, with
import { window } from 'vscode'
if I look atwindow.activeTextEditor.selection
it has the following typewhereas in VSCode, it seems all of these do not have the leading underscore, compare to the defined
TextEditor
interface in@types/vscode
. Why is this difference?