This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-11-12
Channels
- # announcements (2)
- # beginners (104)
- # cider (2)
- # cljs-dev (26)
- # cljsrn (1)
- # clojure (125)
- # clojure-dev (27)
- # clojure-italy (24)
- # clojure-nl (24)
- # clojure-russia (4)
- # clojure-spec (10)
- # clojure-uk (83)
- # clojurescript (18)
- # code-reviews (102)
- # community-development (14)
- # core-async (18)
- # cryogen (11)
- # cursive (15)
- # datomic (16)
- # emacs (6)
- # figwheel-main (6)
- # fulcro (142)
- # graphql (5)
- # jobs (5)
- # jobs-discuss (18)
- # kaocha (1)
- # keechma (1)
- # leiningen (20)
- # luminus (1)
- # mount (5)
- # pedestal (4)
- # reagent (17)
- # reitit (8)
- # shadow-cljs (29)
- # tools-deps (19)
- # vim (108)
Hi! Does mount’s start-with
only start the supplied states or does it start the other states too but without the replace value?
Or more specific to my problem: I have a configuration state Config
and a Database
state which depends on Config
.
For testing I want to start-with
my Config
with testing values. Will the Database
state change when I start the Config
with the custom value?
@pablore start-with
will start everything swapping states in a start-with
map: i.e.
(mount/start-with {#'app.env/config {:db {:uri "test-uri"}}})
will start all the components with {:db {:uri "test-uri"}}
instead of the "original" config state