"Workaround" because I think ultimately the issue is in the Astro language server or an upstream language server returning wrong ranges for completionItem/resolve requests.
Excuse me if there is a reason this behaviour is undesirable. Since the LSP spec says that properties provided in textDocument/completion "must not be changed during resolve" and VS Code presumably (I don't know where its code for handling completions is) behaves like this, as it's not affected by the above issue, I kind of assume this would be fine.
Also, just out of curiosity, is there a reason this doesn't use vim.tbl_extend()?
Fix/workaround for #1705
"Workaround" because I think ultimately the issue is in the Astro language server or an upstream language server returning wrong ranges for
completionItem/resolve
requests.Excuse me if there is a reason this behaviour is undesirable. Since the LSP spec says that properties provided in
textDocument/completion
"must not be changed during resolve" and VS Code presumably (I don't know where its code for handling completions is) behaves like this, as it's not affected by the above issue, I kind of assume this would be fine.Also, just out of curiosity, is there a reason this doesn't use
vim.tbl_extend()
?