This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-06-09
Channels
- # announcements (16)
- # babashka (28)
- # beginners (27)
- # calva (39)
- # chlorine-clover (6)
- # cider (8)
- # clara (28)
- # cljs-dev (19)
- # cljsrn (22)
- # clojure (78)
- # clojure-australia (3)
- # clojure-europe (64)
- # clojure-nl (3)
- # clojure-norway (14)
- # clojure-spec (2)
- # clojure-uk (11)
- # clojurescript (11)
- # core-async (24)
- # datomic (3)
- # deps-new (5)
- # emacs (9)
- # fulcro (4)
- # gis (2)
- # graalvm (9)
- # honeysql (2)
- # hoplon (5)
- # instaparse (1)
- # introduce-yourself (5)
- # jobs (5)
- # luminus (4)
- # observability (7)
- # off-topic (6)
- # pathom (18)
- # pedestal (5)
- # polylith (4)
- # re-frame (2)
- # reagent (1)
- # reitit (1)
- # remote-jobs (7)
- # shadow-cljs (47)
- # specter (1)
- # sql (27)
- # testing (6)
- # tools-deps (4)
- # vim (3)
- # xtdb (8)
Something I think might be helpful for managing the :dev alias in deps.edn: a subcommand in poly that looks through all the bases and components and warns you about any missing src and/or resources paths in :dev and any missing test paths in :test — and in addition gathers up the full set of :deps from bases/`components` and warns about any missing from the :dev alias (and perhaps anything from bricks’ :test aliases that should be under the main :test alias in the workspace-level deps.edn file?).
Good idea!
I guess the sync command that we discussed earlier could help out with that too (for people that want to use it).
If all IDE’s had support for defining the bricks using :local/root then this would be less of a problem, because then the development environment would look very similar to the other projects, except that it also needs to define the test paths (and profiles, if any).