fix: set the right postfix snippets competion source range

[mrnossiom]

Hi 👋,

Changed the completion item source_range to match the replaced text. Though in VS Code it may not be disturbing because the snippet is previewed in a box, but in Helix editor, it's previewed by applying the main text edit.

Before :

After :

Thanks

[Veykril]

Thanks!
@bors r+

[bors]

📌 Commit c5686c8 has been approved by Veykril

It is now in the queue for this repository.

[bors]

⌛ Testing commit c5686c8 with merge 5b08b17...

[bors]

☀️ Test successful - checks-actions
Approved by: Veykril
Pushing 5b08b17 to master...

[pascalkuthe]

thanks for working on this! I just wanted to say that this doesn't just fix the preview (which is just a visual thing) but also multicursor completions.

Additional text edits can't be mapped to multiple cursor (since they aren't associated with the cursor. The spec actually considers this use case. You don't want to repeat imports for each cursor for example).

I see that RA does this as a workaround for LSP only allowing a single edit to each completion item. I think that generally makes sense for associated edits like imports but I can't think of a practical case where multiple edits would be associated with each cursor. I suspect the RA completion edit could be brought closer to the lsp completion edit and avoid impedance mismatches like this bug