This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-24
Channels
- # announcements (4)
- # asami (5)
- # babashka (20)
- # beginners (94)
- # bristol-clojurians (1)
- # calva (23)
- # cider (2)
- # clj-commons (3)
- # clj-kondo (43)
- # cljfx (2)
- # cljs-dev (13)
- # clojure (112)
- # clojure-dev (44)
- # clojure-europe (17)
- # clojure-nl (5)
- # clojure-poland (12)
- # clojure-spec (2)
- # clojure-uk (3)
- # clojurebridge (1)
- # clojurescript (92)
- # cursive (17)
- # data-science (8)
- # datahike (1)
- # datalevin (1)
- # datomic (3)
- # deps-new (7)
- # events (2)
- # fulcro (40)
- # graalvm (110)
- # holy-lambda (16)
- # introduce-yourself (1)
- # lsp (13)
- # malli (8)
- # missionary (12)
- # off-topic (10)
- # pathom (13)
- # polylith (10)
- # portal (28)
- # re-frame (37)
- # reitit (1)
- # releases (1)
- # shadow-cljs (30)
- # spacemacs (1)
- # tools-deps (9)
- # xtdb (10)
Q for... @tengstrand I guess... Is the check
command supposed to take test dependencies into account or is it just "mainline" (src) dependencies? Continued in thread...
As I've been working with my monorepo, which has per-project setup/teardown functions, I often find myself in a situation where check
says OK
but when I run test
, the setup for a project fails because a brick dependency is missing...
...it may just be because of transitive dependencies via legacy subprojects, but I'm not sure what check
's behavior should be...?
As it is now, the check
command doesn’t check for missing libraries, and I don’t think it will in the future either. The original idea with the check command was to check things that the compiler doesn’t check, like that we only access components through their interfaces
in the src
context (the test
context doesn’t have this limitation). The list of checks (errors and warnings) has grown over time and contains https://polylith.gitbook.io/poly/commands#check checks today.
This is essentially a missing brick dependency in a project (not a "library") but it is complicated by our mixed legacy/Polylith setup. I'll see if I can repro in a pure Polylith setup.
Is there any info on workspace.edn and how that works, I am curious how people work with projects do you run commands from the project folder, I noticed workspace.edn has the projects defined so wondered if you can work on the project with out entering the projects folder and running clojure -M:prod -mexample.core type commands
The poly
tool explains it https://polylith.gitbook.io/poly/architecture/workspace.
ah okay, I see the urls are slightly different and i believe this has what I need on building from the workspace root 🙂
I did look on https://polylith.gitbook.io/polylith/architecture/2.1.-workspace I am either missing it or workspace.edn is described else where