Add missing move-form clojure-lsp refactoring#2016
Add missing move-form clojure-lsp refactoring#2016svdo wants to merge 3 commits intoBetterThanTomorrow:devfrom
Conversation
|
Hi Calva team, can you have a quick look at my first commit on this branch please? I'm wondering if this is all there's to its (to add the refactoring commands on the Calva side), or if I'm missing things. Next, I will compare the list in Clojure-lsp and see if there are more missing refactorings. Also, it seems to me that |
PEZ
left a comment
There was a problem hiding this comment.
LGTM so far. There was a thread on the refactorings over at the Clojurians Slack the other day, where some other missing refactors were missing. Don't know if you want to address them at the same time. It's fine with me either way.
|
And now I saw your questions, @svdo. Will have a look. |
6931d3a to
08a45ec
Compare
08a45ec to
71bf46c
Compare
|
Today I had some time to look into this again. I discovered that in fact the destructure-keys and restructure-keys refactorings are available through the quick fix menu. On Slack I found someone mention that |
@svdo I tried using the commands for moving a form to the previous
What do you mean here? On another note, there are some merge conflicts. Would you mind fixing those? |
|
@bpringe This problems I mentioned were a few weeks ago. I'm not sure what was going on, but when I looked at it again this week it seemed to be working fine, so you can ignore those remarks. Regarding the merge conflict: apparently the file I changed has been deleted. Git is not very smart that way :( I tried making the changes again by merging in |
What has changed?
Clojure-lsp has a move-form refactoring that doesn't have an equivalent command in Calva yet. This PR adds the refactoring.
Fixes #2015
My Calva PR Checklist
devbranch. (Or have specific reasons to target some other branch.)published. (Sorry for the nagging.)[Unreleased]entry inCHANGELOG.md, linking the issue(s) that the PR is addressing.ci/circleci: buildtest.If I am fixing just part of the issue, I have just referenced it w/o any of the "fixes” keywords.npm run prettier-format)npm run eslintbefore creating your PR, or runnpm run eslint-watchto eslint as you go).Ping @PEZ, @bpringe, @corasaurus-hex, @Cyrik