Michael Sloan 7f44e4b89c Fix logic for updating insert_range on completion resolution (#32523) ... I don't have a concrete misbehavior from it, but this update of `insert_range` doesn't make sense for two reasons: * If the resolved completion doesn't have a new `text_edit` it would clear out the `insert_range`. * It doesn't update the completion if it has already been resolved, except this update of `insert_range` happened before that. Guessing it was written this way because this field needed to only be mutated within the `CompletionSource::Lsp` case and this was a convenient match below. Release Notes: - N/A Co-authored-by: Smit <smit@zed.dev>		2025-06-23 01:18:47 +00:00
..
src	Fix logic for updating insert_range on completion resolution (#32523)	2025-06-23 01:18:47 +00:00
Cargo.toml	debugger: Use Delve to build Go binaries (#32221)	2025-06-09 21:49:04 -06:00
LICENSE-GPL	chore: Change AGPL-licensed crates to GPL (except for collab) (#4231)	2024-01-24 00:26:58 +01:00