This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-11
Channels
- # ai (1)
- # announcements (59)
- # aws (3)
- # babashka (16)
- # beginners (36)
- # calva (29)
- # cider (7)
- # clj-kondo (33)
- # clojure (77)
- # clojure-austin (1)
- # clojure-australia (4)
- # clojure-europe (16)
- # clojure-france (7)
- # clojure-nl (2)
- # clojure-spec (1)
- # clojure-sweden (8)
- # clojure-uk (4)
- # clojurescript (17)
- # cloverage (4)
- # conjure (2)
- # cursive (3)
- # datomic (22)
- # emacs (16)
- # fulcro (10)
- # graphql (3)
- # helix (13)
- # jobs (1)
- # kaocha (1)
- # lsp (7)
- # malli (1)
- # nextjournal (1)
- # off-topic (32)
- # pedestal (8)
- # polylith (5)
- # reitit (4)
- # reveal (1)
- # shadow-cljs (67)
- # spacemacs (7)
- # tools-deps (6)
- # xtdb (4)
Hi! One thing I haven’t understood from looking at the docs and example projects: am I supposed to put lib dependencis in both bases/components deps and in the root deps.edn under the dev profile?
To get the IDE integration to work with Cursive, you need to add components as :extra-paths
for the :dev
alias. If you use another IDE, it should work adding them as :extra-deps
by specifying each component as :local-root
for the :dev
alias. If you use Cursive, you need to specify the test directories for each component also in the :test
alias as`:extra-paths` to get the IDE integration to work. I don’t think you have to do that if you use e.g. Calva, because it uses another way of understanding the code than Cursive. So if any developer in your team(s) use Cursive, then you probably have to add the components as :extra-paths
in deps.edn
, otherwise adding them as :extra-deps
should be enough.
Yes, I totally agree!