Add #[derive(Debug)] code action only triggers on line start

[eduardorittner]

The code action to add #[derive(Debug)] for a struct which needs it only shows up when the cursor is on the first character of the line (in this case, the 's' of the struct keyword), while the intuitive behavior would be to suggest this action when hovering over the struct definition: only the struct's name or (preferably) anywhere in the struct definition. The same behavior is also true for enums as well.

rust-analyzer version: rust-analyzer 1.89.0 (2948388 2025-08-04)

rustc version: rustc 1.89.0 (29483883e 2025-08-04)

editor or extension: Helix and Neovim

relevant settings: All default settings

code snippet to reproduce:

struct MyData {
    data: usize,
}

fn main() {
    let data = MyData { data: 0 };
    println!("{data:?}");
}

[ChayimFriedman2]

We don't suggest any code action when hovering, if you meant in the IDE definition of "hover". Anyway, this is intentional. We already have too many assists, therefore we need to limit their scope. Allowing it everywhere in the struct definition seems too much.

[MarSik]

Then please expand it to at least the struct name. I agree with the reporter that it is the most logical place I place the cursor at when looking for an action like that.

There is an argument that could be made about discoverability that is related to exactly what you said. There are a lot of assists to remember and it is becoming less and less obvious what to do to be able to trigger them.

[ChayimFriedman2]

I don't know what you are witnessing. I see two code actions: one by rust-analyzer, "Add #[derive]", and another by rustc, "consider annotating MyData with #[derive(Debug)]: #[derive(Debug)]. Both are offered on the struct name.