The slint-nightly vscode extension now can be loaded as a web extension on the online vscode on e.g https://vscode.dev .
The slint-nightly extension can be loaded and the wasm LSP works well for file loaded from with the "file / open" menu (eg: local files)
so one can have auto-completion, error reporting, and go to symbol.
But it doesn't work for file loaded from a git repository for some reason.
The extension is loaded. the LSP worker is started. The initialize() callback is called and we call and return from the wasm properly for this call. But no further callback are recieved on the lsp worker.
(In that screenshot, the breakpoint line 8250 is hit, and we can check that ths_lsp is properly created and that the call to capabilities() actually return the right result. But no further breakpoint is hit. Which kind of mean that no further notification was sent.)
ogoffart
commented
2 years ago
The slint-nightly vscode extension now can be loaded as a web extension on the online vscode on e.g https://vscode.dev . The slint-nightly extension can be loaded and the wasm LSP works well for file loaded from with the "file / open" menu (eg: local files) so one can have auto-completion, error reporting, and go to symbol. But it doesn't work for file loaded from a git repository for some reason.
The extension is loaded. the LSP worker is started. The initialize() callback is called and we call and return from the wasm properly for this call. But no further callback are recieved on the lsp worker.
(In that screenshot, the breakpoint line 8250 is hit, and we can check that
ths_lspis properly created and that the call to capabilities() actually return the right result. But no further breakpoint is hit. Which kind of mean that no further notification was sent.)Step to reproduce: