You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: crates/rust-analyzer/src/diagnostics/snapshots/rust_analyzer__diagnostics__to_proto__tests__snap_multi_line_fix.snap
Copy file name to clipboardExpand all lines: crates/rust-analyzer/src/diagnostics/snapshots/rust_analyzer__diagnostics__to_proto__tests__snap_rustc_unused_variable.snap
If this capability is set, the assists will be computed lazily. Thus `CodeAction` returned from the server will only contain `id` but not `edit` or `command` fields. The only exclusion from the rule is the diagnostic edits.
107
+
108
+
After the client got the id, it should then call `experimental/resolveCodeAction` command on the server and provide the following payload:
109
+
110
+
```typescript
111
+
interfaceResolveCodeActionParams {
112
+
id:string;
113
+
codeActionParams:lc.CodeActionParams;
114
+
}
115
+
```
116
+
117
+
As a result of the command call the client will get the respective workspace edit (`lc.WorkspaceEdit`).
118
+
119
+
### Unresolved Questions
120
+
121
+
* Apply smarter filtering for ids?
122
+
* Upon `resolveCodeAction` command only call the assits which should be resolved and not all of them?
0 commit comments