This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-07
Channels
- # beginners (73)
- # boot (20)
- # chestnut (8)
- # cider (36)
- # clara (37)
- # cljs-dev (21)
- # cljs-experience (1)
- # cljsrn (2)
- # clojure (163)
- # clojure-austin (3)
- # clojure-dusseldorf (6)
- # clojure-finland (1)
- # clojure-ireland (4)
- # clojure-italy (45)
- # clojure-russia (9)
- # clojure-spec (47)
- # clojure-uk (20)
- # clojurescript (107)
- # cursive (24)
- # data-science (4)
- # datomic (4)
- # defnpodcast (1)
- # fulcro (1)
- # heroku (3)
- # jobs-discuss (4)
- # juxt (52)
- # lein-figwheel (1)
- # leiningen (4)
- # lumo (37)
- # midje (5)
- # off-topic (16)
- # onyx (15)
- # portkey (11)
- # re-frame (112)
- # reagent (12)
- # rum (1)
- # specter (35)
- # uncomplicate (6)
i have ring middleware that rebinds a function (`fetch/get`) depending on stuff in the request map
but (against-background (fetch/get "foo") => "bar")
does not appear to work, and it goes ahead and does the middleware bound (fetch/get)
i can't really follow what's going on in the midje source, so i guessed that maybe midje was rebinding (fetch/get)
itself, so I added some metadata {:unassigned true}
and only rebound fetch/get
in my middleware when that was true. However, it still seems to have this metadata with (against-background)
set, so I must have a faulty model in my mind of how midje is working here