This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-23
Channels
- # beginners (27)
- # boot (8)
- # cider (17)
- # cljs-dev (8)
- # cljsrn (5)
- # clojure (56)
- # clojure-dev (34)
- # clojure-gamedev (4)
- # clojure-italy (32)
- # clojure-nl (22)
- # clojure-poland (3)
- # clojure-russia (17)
- # clojure-spec (31)
- # clojure-uk (48)
- # clojurescript (47)
- # core-async (41)
- # cursive (13)
- # datomic (22)
- # emacs (9)
- # figwheel (7)
- # fulcro (18)
- # graphql (3)
- # hoplon (15)
- # jobs-discuss (38)
- # keechma (1)
- # luminus (10)
- # off-topic (42)
- # onyx (8)
- # overtone (3)
- # protorepl (5)
- # re-frame (42)
- # reagent (6)
- # reitit (3)
- # schema (4)
- # shadow-cljs (39)
- # slack-help (5)
- # spacemacs (8)
- # specter (1)
- # tools-deps (36)
- # uncomplicate (9)
- # vim (34)
Haven’t been using Cursive for a long time. Is it able to rename namespaces across clj/cljc/cljs and all the requires that belong to it?
@borkdude just did a quick test renaming a cljc namespace, it seems to work, even the namespace of the test clj was changed.
@borkdude Cursive doesn’t support this very well, at least yet. You can only really rename the last segment of a namespace name, since anything else requires moving things around. clj-refactor supports this for clj I think, but not cljs or cljc. cljc is actually pretty hard to do right.
I'd so love refactoring to work. It gets super fiddly to manage namespace uses especially if you have ::local-keyword
in the code. Expanding them to fully qualified keywords helps but that's fiddly to do manually too.
Can I somehow tell Cursive to search clj, cljc and cljs files for references when talking about keywords?
now it depends on the file type if it finds it or not, which is kinda annoying in full-stack clojure project when for example renaming a keyword or searching where it is used
I've ended up using "find in path" and "replace in path" but that is more than sub-optimal solution
@niklas.collin It shouldn’t be scoped by file type, I’ll check that.