This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-27
Channels
- # aleph (7)
- # beginners (80)
- # boot (1)
- # cider (3)
- # cljs-dev (277)
- # cljsjs (52)
- # cljsrn (1)
- # clojure (69)
- # clojure-gamedev (4)
- # clojure-italy (1)
- # clojure-losangeles (2)
- # clojure-russia (89)
- # clojure-spec (92)
- # clojure-uk (196)
- # clojured (1)
- # clojurescript (70)
- # cursive (5)
- # data-science (1)
- # datascript (84)
- # datomic (9)
- # defnpodcast (12)
- # docker (1)
- # emacs (4)
- # events (1)
- # fulcro (112)
- # graphql (1)
- # jobs (1)
- # lumo (1)
- # nrepl (21)
- # off-topic (2)
- # onyx (3)
- # protorepl (10)
- # re-frame (23)
- # reagent (66)
- # reitit (2)
- # rum (13)
- # shadow-cljs (144)
- # spacemacs (14)
- # sql (4)
- # unrepl (29)
- # vim (16)
In the "Testing Without Mocking" section of the docs it indicates to re-associate input and output plugins with in-memory plugins in order to test the interface. Is there a particular way to do this or is it mostly achieved by having different configuration files for the catalog depending on the environment? And if that's the case I'm guessing it's not possible to use the "add-task" function any longer since it would be necessary to execute different code according to the environment
I’ve just finished a first draft at an environment variable that will disable the kill button on the onyx-dashboard here: https://github.com/onyx-platform/onyx-dashboard/pull/87