This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-09
Channels
- # announcements (5)
- # beginners (53)
- # clj-kondo (4)
- # cljdoc (3)
- # cljs-dev (11)
- # cljsjs (1)
- # clojure (59)
- # clojure-europe (15)
- # clojure-italy (6)
- # clojure-nl (9)
- # clojure-spec (22)
- # clojure-uk (26)
- # clojurescript (16)
- # clojutre (6)
- # cursive (27)
- # datomic (34)
- # duct (1)
- # figwheel-main (2)
- # fulcro (12)
- # graphql (14)
- # jackdaw (9)
- # jobs (1)
- # kaocha (4)
- # luminus (1)
- # off-topic (11)
- # pathom (1)
- # pedestal (2)
- # re-frame (6)
- # reagent (10)
- # ring-swagger (34)
- # shadow-cljs (47)
- # spacemacs (21)
- # sql (3)
- # tools-deps (37)
- # uncomplicate (11)
- # vim (17)
I wanted to double check if this is OK - if I want to noop from an interceptor (essentially skip an event) I can return nil from the :before?
Ah, I meant that I wanted the handling of the event to be a noop, like re-frame doesn’t continue handling anymore effects for that context. nil presumably works because you’ve returned something with no more effects, but wasn’t sure if that was more of a hack or an intended thing.
I'm getting some unusual behavior with reframe http fx. I'm doing a GET request and the :on-success handler gets passed in a response that doesn't match what the browser console shows. The response format is EDN. I have a :db/id and :foo.bar/id with the same integer value. Where it gets odd is that both are incremented. For example if :db/id and :foo.bar/id are supposed to be 70000000000000000, it is 70000000000000001 instead.