Open angelozerr opened 2 years ago
@fbricon I think linkedediting range should be used when user do a rename to provide inline rename.
When user process a rename, we should try to consume linked editing range at first (if language server have the proper capability) and if cannot we consume prepare rename.
What do you think about this idea?
those 2 are triggered differently. So it's not a question of trying one before the other. We should not try to add a fallback mechanism IMO
vscode activate linked editing range on each cursor changes.
We could do that, but it means that we need to implement a debounce mechanism to avoid consuming linked editing range too many and have horrible performance.
For me linked editing range is the same thing as inline rename.
It should be nice to support
textDocument/linkedEditingRange
to support for instance https://github.com/redhat-developer/vscode-quarkus/blob/master/docs/qute/TemplateSupport.md#linked-editingSee https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_linkedEditingRange