This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-30
Channels
- # admin-announcements (3)
- # arachne (8)
- # beginners (5)
- # boot (52)
- # braveandtrue (4)
- # cider (17)
- # cljsrn (1)
- # clojure (36)
- # clojure-dusseldorf (2)
- # clojure-india (1)
- # clojure-russia (30)
- # clojure-uk (1)
- # clojurebridge (1)
- # clojurescript (47)
- # clojutre (1)
- # component (1)
- # core-async (3)
- # cursive (5)
- # datascript (1)
- # datomic (4)
- # emacs (1)
- # error-message-catalog (62)
- # garden (3)
- # hoplon (16)
- # jobs (5)
- # luminus (11)
- # mount (1)
- # om (32)
- # onyx (17)
- # spacemacs (4)
- # untangled (20)
- # yada (4)
@ido thanks for the detailed explanation. if I understood you correctly you have mount states within a jar (with common deps), and you are getting mount.core.NotStartedState
when you are trying to access these states from within an app that depends on those jars.
(in case I understood the problem correctly) I would split my answer in two:
1. While it is not a usual usage of states, it should still work if things are required correctly: https://gist.github.com/tolitius/a5fe7dfab29be1402bd2f560a64e6900
2. I agree with @dm3 that it looks like you could solve it a bit differently. Rather then passing states around, you could have states depend on app configuration. i.e. your app will have a config.edn
that would have various configs for kafka, db and such. i.e. https://github.com/tolitius/cprop