This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-24
Channels
- # announcements (31)
- # babashka (21)
- # babashka-sci-dev (4)
- # beginners (8)
- # cherry (4)
- # cider (32)
- # clj-kondo (15)
- # cljdoc (4)
- # cljsrn (4)
- # clojure (69)
- # clojure-dev (1)
- # clojure-europe (12)
- # clojure-nl (1)
- # clojure-norway (8)
- # clojure-uk (4)
- # clojurescript (16)
- # clr (6)
- # conjure (4)
- # fulcro (4)
- # hispano (1)
- # honeysql (1)
- # humbleui (5)
- # hyperfiddle (8)
- # lambdaisland (4)
- # lsp (8)
- # malli (24)
- # off-topic (3)
- # polylith (5)
- # reagent (10)
- # remote-jobs (3)
- # rewrite-clj (7)
- # scittle (12)
- # spacemacs (4)
- # sql (2)
- # tools-deps (29)
- # xtdb (7)
given :main-opts
in my :test
alias and none in my :dev
alias, is there a way for me to start with clojure.main so I can do clj -M:dev:test -e ,,,
? clj -M:test:dev
will run :main-opts
from :test
which I don’t want.
Optimally you should be able to:
clj -A:dev:test -M -e
but currently -A: still runs :main-opts
which I hope will be removed sooner than laterUse -r
to start a REPL: clj -A:dev:test -r
@U04V70XH6 -A:dev:test will still kick off the :main-opts of the :test alias, no?
Hmm, I shouldn't offer advice at 6 am without coffee. I use -r
on some projects but I think maybe I have an empty :main-opts
in an alias and use that to override previous :main-opts
I will now either go back to bed for a few hours or make a ☕
Unfortunately the -X hack didn't work, I'm getting:
Unqualified function can't be resolved: -M
@U064X3EF3 When can we get -A with ignorance of :main-opts? 🙏
After add-libs :)
Can’t you just split into two aliases as a workaround? Seems like you’re making this so hard
Still hoping this will happen soon. See discussion in https://app.slack.com/client/T03RZGPFR/C02FBBU61A9/thread/C02FBBU61A9-1689157272.648009 cc @U5H74UNSF @U3X7174KS
Why are the resources
and target
dirs included in :paths ["src" "resources" "target"]
in the documentation of figwheel? Isn't this option for listing source code directories?
https://figwheel.org/docs/create_a_build.html
Did you mean to ask that in the #CALJ3BFLP channel?
Sure, but only Figwheel users (or possibly only the Figwheel maintainers) will know the answer to this.
:paths
just puts folders on the classpath so they're available when running code.
(so, no, it's not just source code directories -- it's anything you want on the classpath)
Having target
on the classpath sounds a bit odd to me but I guess it depends what Figwheel puts into that folder.
If you've been using Leiningen (or Boot) previously, maybe this old blog post of mine will shed some light? https://corfield.org/blog/2018/04/18/all-the-paths/