This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-25
Channels
- # beginners (26)
- # boot (1)
- # cider (21)
- # cljdoc (26)
- # cljs-dev (7)
- # clojure (99)
- # clojure-gamedev (6)
- # clojure-italy (5)
- # clojure-nl (4)
- # clojure-russia (1)
- # clojure-spec (5)
- # clojure-uk (59)
- # clojurescript (49)
- # clojutre (6)
- # component (13)
- # core-async (2)
- # cursive (30)
- # data-science (2)
- # datomic (29)
- # emacs (9)
- # fulcro (100)
- # hyperfiddle (1)
- # jobs (2)
- # luminus (4)
- # lumo (23)
- # off-topic (22)
- # other-languages (37)
- # parinfer (1)
- # re-frame (2)
- # reagent (5)
- # reitit (12)
- # ring (12)
- # rum (3)
- # shadow-cljs (168)
- # slack-help (1)
- # spacemacs (7)
- # specter (2)
- # tools-deps (8)
- # vim (11)
- # yada (3)
With a system map, when u have system using, how do you know which component will be started first and last?
I don't think it should matter as long as all your dependencies are declared
why would you have an ordering requirement that doesn't correspond to a dependency?
(even if you do, you could add an artificial dependency to enforce the ordering)
I have a builder which starts first, then a stream that starts next, which both go into a topology. I think that as the topology has the most deps it will start later, is that correct?
>why would you have an ordering requirement that doesn’t correspond to a dependency? I’m not sure what you mean sorry
if component A depends (in the system/using sense) on component B, then component B will always start first
when the start
function is called on a component, all its dependencies are present and have already started