This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-18
Channels
- # 100-days-of-code (10)
- # announcements (2)
- # aws (3)
- # beginners (120)
- # boot (6)
- # calva (6)
- # cider (22)
- # cljsrn (3)
- # clojure (145)
- # clojure-greece (1)
- # clojure-italy (7)
- # clojure-nl (24)
- # clojure-russia (90)
- # clojure-spec (21)
- # clojure-uk (80)
- # clojurescript (175)
- # core-async (1)
- # datomic (17)
- # emacs (8)
- # ethereum (5)
- # figwheel (1)
- # figwheel-main (140)
- # fulcro (137)
- # jobs (6)
- # jobs-discuss (3)
- # luminus (3)
- # mount (1)
- # nyc (3)
- # off-topic (39)
- # onyx (1)
- # pedestal (1)
- # re-frame (21)
- # reagent (13)
- # shadow-cljs (60)
- # spacemacs (25)
- # test-check (4)
- # tools-deps (14)
- # uncomplicate (3)
- # vim (18)
Hello, I ran into a little hiccup with mount. I am in the REPL and I have two projects that both use mount and one proj depends on the other. I was thinking mount only respected the currently loaded namespace, but it seems I can be in any namespace and mount/start
just starts everything which is a mess. I worked around this initially by just maintaining a list of states in my libary's entrypoint and calling start only these states
.. but that's a little tedious with a lot of states. This example shows the ideal usage for packaging a library https://github.com/tolitius/mount#packaging ... I haven't got that working. Using the same setup as the example, a call to mount/start
in a library starts all the states the REPL knows about it seems like. Is it because I am using checkouts. Regardless, I think being able to restart only the state that the current namespace depends on would be a great feature. Any ideas? Thanks