Piotr Osiewicz f3320998a8 lsp: Track completion triggers for each language separately (#20471) ... This PR improves how we handle completions in buffers with multiple LSPs. Context: while working on https://github.com/zed-industries/zed/issues/19777 with @mgsloan we noticed that completion triggers coming from language servers are not tracked properly. Namely, each buffer has `completion_triggers` field which is read from the configuration of a language server. The problem is, there can be multiple language servers for a single buffer, in which case we'd just stick to the one that was registered last. This PR makes the tracking a bit more fine-grained. We now track not only what the completion triggers are, but also their origin server id. Whenever completion triggers are updated, we recreate the completion triggers set. Release Notes: - Fixed completions not triggering when multiple language servers are used for a single file.		2024-11-10 10:29:10 +01:00
..
proto	lsp: Track completion triggers for each language separately (#20471)	2024-11-10 10:29:10 +01:00
src	proto: Remove unused UpdateUserSettings message (#20005)	2024-10-31 09:36:18 +01:00
build.rs
Cargo.toml
LICENSE-GPL