aboutsummaryrefslogtreecommitdiff
path: root/test/functional/vimscript/executable_spec.lua
diff options
context:
space:
mode:
authorYi Ming <ofseed@foxmail.com>2026-04-02 20:53:29 +0800
committerGitHub <noreply@github.com>2026-04-02 08:53:29 -0400
commit0eb2eb4106a303f5d99a3e108ebd10654d627cde (patch)
tree2574af960329bdade7b589024dd328af8be910fe /test/functional/vimscript/executable_spec.lua
parent2cf5dcb1708c6f94429e9ef38318fdf1f7601ef8 (diff)
downloadrneovim-0eb2eb4106a303f5d99a3e108ebd10654d627cde.tar.gz
rneovim-0eb2eb4106a303f5d99a3e108ebd10654d627cde.tar.bz2
rneovim-0eb2eb4106a303f5d99a3e108ebd10654d627cde.zip
refactor(lsp): remove implicit rpc error tostring #38707
Problem: LSP error responses implicitly rely on a custom `__tostring` function (`vim.lsp.rpc.format_rpc_error`) for formatting. This causes errors that are not created via `vim.lsp.rpc.error` to behave inconsistently with those that are. Furthermore, we usually use `log.error` to print these errors, which uses `vim.inspect` under the hood, so the custom `__tostring` provides little benefit. This increases the difficulty of refactoring the code, as it tightly couples RPC error handling with the LSP. Solution: Convert every potential `__tostring` call to an explicit one. Since we don't describe this behavior in the documentation, this should not be a breaking change.
Diffstat (limited to 'test/functional/vimscript/executable_spec.lua')
0 files changed, 0 insertions, 0 deletions