This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-02
Channels
- # announcements (2)
- # beginners (32)
- # boot (10)
- # calva (81)
- # cider (39)
- # clojure (56)
- # clojure-europe (8)
- # clojure-italy (7)
- # clojure-new-zealand (1)
- # clojure-nl (8)
- # clojure-poland (1)
- # clojure-spec (12)
- # clojure-uk (38)
- # clojurescript (5)
- # community-development (1)
- # core-async (55)
- # cursive (3)
- # datomic (44)
- # dirac (15)
- # emacs (20)
- # events (1)
- # fulcro (57)
- # hyperfiddle (2)
- # jobs (9)
- # juxt (9)
- # kaocha (1)
- # lein-figwheel (1)
- # off-topic (93)
- # pathom (2)
- # pedestal (3)
- # planck (3)
- # reitit (15)
- # ring (10)
- # shadow-cljs (25)
- # spacemacs (7)
- # sql (19)
- # tools-deps (8)
@conan is the feature of mount where reset is run each time a file changes easily configurable? I'd prefer more control over when I do a reset vs compile an individual namespace.
you can exclude a specific component with metadata which i've done before, but mostly i've been happy with how it works. what sort of situation are you thinking of where you wouldn't want the component to restart, have you come across necessarily long-running components before?
here's the relevant bit of the docs https://github.com/tolitius/mount#recompiling-namespaces-with-running-states
the library itself is actually really nice, it results in a lot less code and configuration. i expect when systems get large and fine-grained control is needed it might get limiting, but i always find myself in microservice environments these days so it never seems to happen ¯\(ツ)/¯