Christian Dietrich
Christian Dietrich
client and server just need to make sure they are on same if they send and expect content length in the past monaco-language client did have the problem it could...
no i mean other way round. in websocket mode it does not expect it. => what happens if you strip it out at WebSocketMessageHandler and readd it at WebSocketMessageConsumer
cause monaco-language client does NOT wanna have /send the content length? it at least was when i checked back in 2020 or so the classes are hooked up at WebSocketLauncherBuilder
i dont know the websocket feature is vscode so i cannot tell. the websocket feature here was developed with monaco language client in mind. i propose you debug what comes...
how does your client look like?
xbase/xtend.lib no longer is a runtime dependency
see also didClose in https://github.com/eclipse-langium/langium/discussions/1281
i will check
i wonder if we can have access to both the current and following token. thus we can decide if we need a space between two alphanumeric things or not. or...
this is also hard to achieve. backtrackToAnyToken wont give a whitespace token something like ``` protected override async completionFor(context: CompletionContext, next: NextFeature, acceptor: CompletionAcceptor): Promise { const { nextTokenStart, previousTokenStart,...