lsp-devtools
lsp-devtools copied to clipboard
swyddfa
Tooling for working with language servers and clients.
I'll try to debug further, but when I try to use `lsp-devtools record --to-file` to record a session connecting my LSP server to a client file which contains unicode I...
It would be good to have some feedback on if there is a client connection or not.
If there is an active TCP connection, it requires multiple `Ctrl+C` commands to close stop the command.
The `lsp-devtools agent` does not work on windows, due to the way it currently tries to obtain async readers/writers for stdin/stdout.
It would be useful for `lsp-devtools` to be able to read configuration from say `pyproject.toml`. This would open the possibility of introducing named profiles as shortcuts to common use-cases e.g....
Currently, any message that does not match a format string given to `lsp-devtools record` is not shown. This is useful, however there are situations where you want the message to...
It would be nice to specify multiple [format strings](https://lsp-devtools.readthedocs.io/en/latest/lsp-devtools/guide/record-command.html#formatting-messages) for use with the `lsp-devtools record` command, having the command use the first one that applies cleanly for each message
Still a valid issue, but the architecture is now different - can we have multiple agents reports into a single server command? ~Since the agent is wrapped in a websocket...
To truly be useful, you'd need to be able to filter the table of messages by some criteria to find the message(s) you're interested in
[Current version](https://github.com/swyddfa/lsp-devtools/blob/e5337065f89f84a45dc798ab4ee6666191be5cd7/lib/pytest-lsp/pytest_lsp/clients/visual_studio_code_v1.65.2.json) is `v1.65.2` - VSCode is now on `v.1.83.0`! It would be good to have some of the intermediate versions as well