Files
oak-gpui/crates
Kirill Bulatov 8a31dcaeb0 Use textDocument/codeLens data in the actions menu when applicable #2 (#26848)
Re-applies what's been reverted in
https://github.com/zed-industries/zed/pull/26832 with an action-related
fix in
https://github.com/zed-industries/zed/commit/64b5d37d324176cc7b819418f46724cd4c67393d

Before, actions were resolved only if `data` is present and either of
the possible fields is empty:

https://github.com/zed-industries/zed/blob/e842b4eade368127f01944f1b442016edd6b292d/crates/project/src/lsp_store.rs#L1632-L1633

But Zed resolves completions and inlays once, unconditionally, and the
reverted PR applied the same strategy to actions.
That did not work despite the spec not forbidding `data`-less actions to
be resolved.

Soon, it starts to work due to
https://github.com/rust-lang/rust-analyzer/pull/19369 but it seems safer
to restore the original filtering code.

Code lens have no issues with `data`-less resolves:

https://github.com/rust-lang/rust-analyzer/blob/220d913cbcd05f9b7635179a98c685f31821a572/crates/rust-analyzer/src/handlers/request.rs#L1618-L1620

so the same approach as completions and inlays is kept: resolve once.


Release Notes:

- N/A
2025-03-15 20:09:32 +00:00
..
2025-03-06 05:20:06 +00:00
2025-02-28 18:33:35 +01:00
2025-03-06 10:56:28 -07:00
2025-01-27 13:40:59 -05:00
2025-03-13 15:52:47 -06:00
2025-03-12 07:25:19 +00:00
2025-03-10 13:38:30 -06:00
2025-03-13 15:52:47 -06:00
2025-02-28 18:33:35 +01:00
2025-03-14 15:18:55 +00:00
2025-02-28 18:33:35 +01:00
2025-03-11 21:39:29 +00:00
2025-03-10 13:38:30 -06:00
2025-03-13 15:52:47 -06:00
2025-03-13 15:52:47 -06:00
2025-03-15 05:58:34 +00:00
2025-03-06 10:56:28 -07:00
2025-03-10 13:19:02 -07:00
2025-03-13 15:52:47 -06:00
2025-03-15 05:58:34 +00:00
2025-03-14 17:55:52 -04:00
2025-03-13 15:52:47 -06:00
2025-03-10 13:38:30 -06:00