LSP Extensions support

• https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/dev/lsp-extensions.md
• https://github.com/rust-analyzer/rust-analyzer/issues/4604

Name	PR	Status
SnippetTextEdit	https://github.com/rust-analyzer/rust-analyzer/pull/4494	Done #252
CodeAction Groups	https://github.com/rust-analyzer/rust-analyzer/pull/4569	No Plan
Parent Module	https://github.com/rust-analyzer/rust-analyzer/pull/4611	Done 14001ac
Join Lines	https://github.com/rust-analyzer/rust-analyzer/pull/4557	Done #259
On Enter	https://github.com/rust-analyzer/rust-analyzer/pull/4607	No Plan
SSR	https://github.com/rust-analyzer/rust-analyzer/pull/4560	Done c47c988
Matching Brace	https://github.com/rust-analyzer/rust-analyzer/pull/4593	Done ad3656e
Runnables	https://github.com/rust-analyzer/rust-analyzer/pull/4710	Done d9e8102
Lazy assists with ResolveCodeAction	https://github.com/rust-analyzer/rust-analyzer/pull/4717	Done ddd83c5
Hover Actions	https://github.com/rust-analyzer/rust-analyzer/pull/4729	Done 06b4c92
Reload Workspace	https://github.com/rust-analyzer/rust-analyzer/pull/5169	Done 15bd717
Status Notification	https://github.com/rust-analyzer/rust-analyzer/pull/5188	Done 3a055d6
Analyzer Status	https://github.com/rust-analyzer/rust-analyzer/pull/6096	Done 473a2a8
Open External Documentation	https://github.com/rust-analyzer/rust-analyzer/pull/5917	Done 04c51ad
Open Cargo.toml	https://github.com/rust-analyzer/rust-analyzer/issues/6462	Done 35958ab
Syntax Tree		Done
Expand Macro		Done
Inlay Hints		chainingHints #220 typeHints eeda508664e6bcb8a9d5059455202c34921db0ae
View Hir	https://github.com/rust-analyzer/rust-analyzer/pull/7068	Done f5720cc
View File Text	https://github.com/rust-lang/rust-analyzer/pull/11861	Done 3a69d37
Related tests	https://github.com/rust-analyzer/rust-analyzer/pull/7799	Done c00285d
Hover Actions	https://github.com/rust-analyzer/rust-analyzer/pull/8054	Done f65c4c2
View Crate Graph	https://github.com/rust-analyzer/rust-analyzer/pull/8801	Done 198bf44 70a051e
View ItemTree	https://github.com/rust-analyzer/rust-analyzer/pull/8916	Done 8b49b7d
Lookup workspace symbol	https://github.com/rust-analyzer/rust-analyzer/pull/7698	Done a1b7e16
Hover Range	https://github.com/rust-analyzer/rust-analyzer/pull/9693	Done #839
Run flycheck	https://github.com/rust-lang/rust-analyzer/pull/13792	Done e259fca
Cancel running flychecks	https://github.com/rust-lang/rust-analyzer/pull/13063	Done 73248ba
Clear flycheck diagnostics	https://github.com/rust-lang/rust-analyzer/pull/13792	Done e259fca

[fannheyward]

@HungPham3112 the snippets are came from rust-analyzer, post your feature request to rust-analyzer.

[resolritter]

the problem is I did find a better way to make Range hover work with nnoremap K. Do you have any ideas?

You’re using getSelectedRange while expecting Vim to be in visual mode, however :<C-U> kind of mappings (e.g. xmap <Plug>(coc-codeaction-selected)) exit visual mode before executing the range and therefore that check will not pass.

While you could use <cmd> mappings to avoid exiting visual mode, exiting is needed to get the visual mode range with '< and '> like here (as far as I’m aware it’s not possible to do that while staying in visual mode, you have to exit it first for those marks’ positions to be updated).

So, in short, the solution is to make the mapping work like xmap <Plug>(coc-codeaction-selected) where you’ll detect visualmode() when the mapping is triggered, not after. Here’s the doCodeAction code for reference and you’ll see that it fetches the visual range using the marks’ positions as mentioned.