Describe the bug
A symbol renaming works is limited to a single file
To Reproduce
Steps to reproduce the behavior:
- Have a struct/class defined
- create its reference in another file
- call rename
Expected behavior
A symbol is renamed in all the files - where it's defined and referenced.
Actual behavior
A symbol is renamed in a single file where it's defined.
Configuration
"zls": {
"type": "stdio",
"command": "mcp-language-server",
"args": [
"--workspace",
"directory",
"--lsp",
"zls"
],
"env": {}
},
Additional context
prompt example: use zls mcp to rename Block struct in @src/store/inmem/block.zig to RawBlock.
My guess is workspace edit client capabilities are not defined explicitly so that LSP falls back to a single file renaming, but Im not sure.
I can try configuring client if you accept a PR
Describe the bug
A symbol renaming works is limited to a single file
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A symbol is renamed in all the files - where it's defined and referenced.
Actual behavior
A symbol is renamed in a single file where it's defined.
Configuration
Additional context
prompt example: use zls mcp to rename Block struct in @src/store/inmem/block.zig to RawBlock.
My guess is workspace edit client capabilities are not defined explicitly so that LSP falls back to a single file renaming, but Im not sure.
I can try configuring client if you accept a PR