This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-24
Channels
- # architecture (7)
- # beginners (73)
- # boot (4)
- # cider (48)
- # cljsjs (7)
- # cljsrn (27)
- # clojure (206)
- # clojure-boston (2)
- # clojure-italy (21)
- # clojure-nl (8)
- # clojure-spec (7)
- # clojure-uk (94)
- # clojurescript (126)
- # clojutre (7)
- # core-async (3)
- # cursive (7)
- # data-science (1)
- # datascript (4)
- # datomic (6)
- # duct (1)
- # emacs (19)
- # figwheel (1)
- # fulcro (31)
- # graphql (13)
- # jobs (5)
- # jobs-discuss (42)
- # keechma (4)
- # leiningen (10)
- # luminus (3)
- # mount (2)
- # nyc (3)
- # off-topic (37)
- # om-next (3)
- # onyx (45)
- # pedestal (2)
- # re-frame (4)
- # reagent (2)
- # reitit (16)
- # shadow-cljs (118)
- # spacemacs (10)
- # tools-deps (8)
- # vim (20)
is there a way to automate changing project names? i do this fairly frequently when i'm just noodling around and although it's really simple i've never not forgotten to change something the first time
tools.namespace has some tools for changing namespace names, I've used them in the past, they seem to work
what do you mean change a projects name?
lets you deploy a fork under a different name
I mean, change essentially everything generated by a call to lein new app
or similar: the defproject
name, :main
value, src dir, and ns
in core.clj
. That's the only way I can imagine to do it uniformally. Once some of that structure changes I can't think of how it would be possible
ah, have never heard of anything that does that
Other than recreating the template with a new name