Andrew Gallant 196a68e4c8 [ty] Render import <...> in completions when "label details" isn't supported ... This fixes a bug where the `import module` part of a completion for unimported candidates would be missing. This makes it especially confusing because the user can't tell where the symbol is coming from, and there is no hint that an `import` statement will be inserted. Previously, we were using [`CompletionItemLabelDetails`] to render the `import module` part of the suggestion. But this is only supported in clients that support version 3.17 (or newer) of the LSP specification. It turns out that this support isn't widespread yet. In particular, Heliex doesn't seem to support "label details." To fix this, we take a [cue from rust-analyzer][rust-analyzer-details]. We detect if the client supports "label details," and if so, use it. Otherwise, we push the `import module` text into the completion label itself. Fixes https://github.com/astral-sh/ruff/pull/20439#issuecomment-3313689568 [`CompletionItemLabelDetails`]: https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#completionItemLabelDetails [rust-analyzer-details]: 5d905576d4/crates/rust-analyzer/src/lsp/to_proto.rs (L391-L404)		2025-10-29 08:50:41 -04:00
..
src	[ty] Render import <...> in completions when "label details" isn't supported	2025-10-29 08:50:41 -04:00
tests/e2e	[ty] Add suggestion to unknown rule diagnostics, rename unknown-rule lint to ignore-comment-unknown-rule (#20948)	2025-10-18 12:44:21 +02:00
Cargo.toml	[ty] Support goto-definition on vendored typeshed stubs (#21020)	2025-10-21 13:38:40 -04:00