Rafał Chłodnicki
Rafał Chłodnicki
Hmm, also not sure now about the behavior of "next_result" command. It doesn't seem to always work for navigating the errors.
I suppose it might have something to do with the diagnostics panel and the scopes used there? I don't honestly know but it doesn't seem to work very reliably according...
But build system results are created at the time of running the build so at least I would expect them to get outdated. LSP is supposed to give live feedback...
As far as fixing or improving this issue, I guess the best we could do is making things clearer to the user somehow. The diagnostic update is obviously delayed a...
I think we could try that but probably would have to have some heuristic as otherwise, it could be too distracting.
I believe the payload for this is: ```js { "label": "String", "filterText": "String", "kind": 22, "additionalTextEdits": [], "textEdit": { "newText": "String", "range": { "start": { "character": 4, "line": 1 },...
@Jcskz can you post the log with the `textDocument/hover` response?
Well, that content triggers the #1473 issue so we have to wait for the next ST build and then re-test this one. I suppose it might just work then (maybe...
I believe that the code block is specified to accept a language identifier and then optionally an info string data after a white space. And this doesn't look anything like...
If we join parent symbol with current symbol then that will affect filtering also. Would that be something we want or should we not join? Unless we want to show...