Dirk Bäumer
Dirk Bäumer
I think https://github.com/eclipse/eclipse.jdt.ls/issues/1864#issuecomment-915098967 answers it. It depends on the client which properties it allows and VS Code DOESN'T support resolving the text edit lazy.
In VS Code it is used to do property prefix matching since the text edit describes the replace region in the document when applying the text edit. Without that info...
This are two things: the spec and the implementation of the vscode node server running on an older TypeScript version. - The specification clearly says that `{"completionProvider": null}` is not...
`Undefined` is (besides at one place in a comment at that should be fixed) not used as a type since it is very JavaScript specific. In general even in TypeScript...
Yes, from a spec point of view `null` is currently not valid. Adding it would be breaking and we need to ensure it is worth the swirl to do this.
Some comments from the specification side: to support the evolution of enumerations a consuming side of an enumeration (usually a server) shouldn't fail on unknown values. If a server does...
Agree :-)
I would actually go with this proposal since it matches the original idea of having named arguments. However we could never unfold them correctly in JS/TS (no reflection) but it...
Wasn't aware of this.
@KievJunta Is this C#?