Repository navigation
Conversation
clj-refactor's commands for editing the ns form now have CIDER counterparts, which clj-refactor 4.1 deprecates its own in favor of. The ns form page gets a table mapping one to the other, the clj-refactor section of the additional packages page says what moved and what's still clj-refactor's, and the FAQ and the roadmap stop listing the move as future work. clj-refactor 4.1 also leaves / alone when cider-ns-magic-requires is on, so the unbinding recipe is only for older versions now.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
clj-refactor's
nsform commands now have CIDER counterparts, so the docs map one to the other, and the FAQ and the roadmap stop listing that move as future work. The page says clj-refactor 4.1 deprecates its versions, which is when this should land.