This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-13
Channels
- # babashka (45)
- # babashka-sci-dev (15)
- # beginners (72)
- # biff (4)
- # calva (3)
- # clj-on-windows (67)
- # clj-otel (1)
- # cljfx (7)
- # clojure (74)
- # clojure-austin (1)
- # clojure-dev (4)
- # clojure-europe (6)
- # clojure-gamedev (1)
- # clojure-germany (5)
- # clojure-losangeles (6)
- # clojure-nl (3)
- # clojure-uk (6)
- # clojured (2)
- # clojurescript (42)
- # core-typed (2)
- # cursive (4)
- # emacs (18)
- # events (1)
- # fulcro (13)
- # humbleui (8)
- # introduce-yourself (2)
- # kaocha (11)
- # leiningen (5)
- # lsp (16)
- # malli (8)
- # off-topic (69)
- # pathom (38)
- # pedestal (3)
- # reagent (17)
- # releases (3)
- # shadow-cljs (10)
- # spacemacs (6)
- # sql (1)
- # tools-deps (5)
- # xtdb (20)
i realize that it's helpful for repl-driven development for :dev
to be in the default profile, but it seems weird to me that :test
also gets access to :dev
. I just ran into an issue where my code runs with lein repl
and lein test
, but fails with lein uberjar
because i had accidentally required one of my dev namespaces in my core code
is there a way to enforce that the test
task only runs with the :test
profile? outside of lein with-profile test test
of course. i'd like to enforce this across my team
I use lein with-profile -dev test
The enforcement is that it runs on CI. Once you get used to some or other incantation, using bare lein test
will feel just wrong
oh yeah, i can subtract! forgot about that. thanks, i'll add that
would lein check
have caught this? I suspect it would have. I often use it because it runs quickly and finds "low hanging fruit" errors that are easier to fix the sooner you find them