This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-21
Channels
- # announcements (26)
- # aws (1)
- # babashka (40)
- # beginners (36)
- # calva (9)
- # cider (38)
- # clara (5)
- # clj-commons (4)
- # clj-kondo (29)
- # cljs-dev (8)
- # cljsrn (2)
- # clojars (12)
- # clojure (151)
- # clojure-europe (16)
- # clojure-gamedev (1)
- # clojure-nl (2)
- # clojure-uk (7)
- # clojurescript (2)
- # copenhagen-clojurians (2)
- # datalevin (18)
- # fulcro (7)
- # graphql (7)
- # gratitude (9)
- # helix (2)
- # honeysql (3)
- # introduce-yourself (1)
- # jobs (1)
- # lsp (13)
- # malli (10)
- # nextjournal (2)
- # off-topic (13)
- # pathom (1)
- # pedestal (2)
- # portal (4)
- # remote-jobs (1)
- # ring-swagger (1)
- # shadow-cljs (21)
- # specter (1)
- # testing (2)
- # tools-build (6)
- # vim (2)
- # xtdb (5)
Are there any plans for b/create-basis
when supplied with :aliases
to combine any :extra-paths
into :paths
for you?
I mean maybe not literally :paths
but an appropriate key.
not sure I understand the question. those should get added to the classpath
are you looking for the "effective paths"?
if so, you can get that with a little bit of effort from the classpath map / classpath keys in the basis
(->> (b/create-basis
{:user {:paths ["src"]
:aliases {:test {:extra-paths ["test"]}}}
:aliases [:test]})
:classpath
(filter (fn [[p src]] (:path-key src)))
(map key))
;;=> ("src/main/clojure" "src/main/resources" "src/test/clojure")
that's not necessarily correct ordering, but the ordering is defined in :classpath-roots
key of the basis