This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-05
Channels
- # announcements (1)
- # babashka (16)
- # beginners (36)
- # biff (1)
- # calva (2)
- # cider (4)
- # cljdoc (1)
- # clojure (118)
- # clojure-austin (2)
- # clojure-czech (2)
- # clojure-europe (19)
- # clojure-norway (3)
- # clojure-spec (8)
- # clojure-uk (3)
- # clojurescript (11)
- # conjure (1)
- # cursive (3)
- # datalevin (5)
- # datomic (7)
- # emacs (16)
- # events (1)
- # figwheel-main (3)
- # fulcro (5)
- # hyperfiddle (17)
- # jobs (2)
- # lsp (19)
- # malli (5)
- # nbb (10)
- # off-topic (5)
- # polylith (5)
- # re-frame (3)
- # reagent (11)
- # remote-jobs (2)
- # shadow-cljs (1)
- # spacemacs (7)
- # web-security (4)
there must have been some questions regarding 'components referring to other components' or situations of circular dependency. What is polylith's policy on those?
The poly
tool will detect and complain about circular dependencies. Does that answer your question?
Thanks for answering. My question was more about whether it is okay(regardless of its possibility) to have one component refer the other in terms of polylith's principle.
Yes, components can refer to each other. That's fine. As long as they are not circular references.
You can see that from the https://polylith.gitbook.io/polylith/conclusion/production-systems page where the middle image in each of the examples is the cross-dependencies of the bricks.