Case Nelson

Yes, if people on old versions start getting annoyed by this we should add it, upvote the issue if it's important to you. However my feeling about our list of...

No suggestions... Here's some random perspectives/ranting. I easily run 5 or 6 instances of clojure-lsp at once. But I will shut down instances when I need to. I only actually...

> although making a partial feature makes user don't rely on that unfortunately It's actually very important to fully move, including aliases and everything. It's not just that they can't...

This is called `move-form` https://github.com/clojure-emacs/clj-refactor.el/wiki/cljr-move-form

> (maybe the first one after sorting) An alternative is not to merge. Otherwise, analysis knows which aliases are used and how often. The add-missing-libspec code does similar work to...

>> lint like "implementations exist but otherwise unused" > > Having another custom lint could be interesting, although I worry that one is very specific to your use case. Future...

You could imagine someone wanting to do this, I believe it is generally frowned upon nest destructurings. ```clojure (defn handler [req] (let [params (get req :params) param1 (get params :param1)]...

> I think those are valid commands, not that sure about code actions yet, but we could start with refactoring commands indeed, one thing to notice is that we would...

Long term, the real solution falls into an idea I've been thinking about to run formatting after refactoring. It's going to take some hammock time to figure out the best...

@Andre0991 @ericdallo My first thought is we'd have to allow macro-defs to add something like an `:extra-info or :return-type` key to the [`add-reference` call](https://github.com/snoe/clojure-lsp/blob/7f28cb3e14ab271eb62cc7afb06fee4bcd239087/src/clojure_lsp/parser.clj#L868-L876), it's possible it has overlap with...