This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-20
Channels
- # adventofcode (47)
- # announcements (3)
- # aws (29)
- # bangalore-clj (3)
- # beginners (63)
- # boot (2)
- # braveandtrue (40)
- # calva (34)
- # cider (37)
- # cljs-dev (8)
- # clojars (3)
- # clojure (45)
- # clojure-europe (2)
- # clojure-france (4)
- # clojure-india (2)
- # clojure-italy (44)
- # clojure-japan (4)
- # clojure-nl (39)
- # clojure-serbia (1)
- # clojure-spec (21)
- # clojure-uk (75)
- # clojurescript (28)
- # cursive (24)
- # data-science (3)
- # datomic (31)
- # emacs (13)
- # fulcro (35)
- # hoplon (21)
- # jobs-discuss (66)
- # nrepl (18)
- # off-topic (72)
- # pathom (35)
- # re-frame (20)
- # reagent (54)
- # shadow-cljs (35)
- # spacemacs (9)
- # specter (8)
- # sql (13)
- # testing (9)
- # tools-deps (21)
- # vim (3)
If I'm in an interceptor and I want to stop the handler from ever firing in some case, what do I need to do something else apart from setting :queue
to nil
and :event
to nil
in the context
. Or is this enough? My handler still seems to be firing - can't get it to stop!
@mateus.pimentel.w Hmm. When I've seen this problem before its been because there's a mixture of React versions. Make sure you are using the version of re-frame-10x
to match the version of React used in your app
Your use of Reagent in your app will be pulling in a particular version of React.
And there are two versions of re-frame-10x
depending on which version of React you are using (15 or 16)
@danieleneal interceptor chain should definitely stop if you set :queue
to nil
https://github.com/Day8/re-frame/blob/master/src/re_frame/interceptor.cljc#L99
@mikethompson Thanks! Good to know that is correct approach. Problem between keyboard and chair - I was setting :coeffects :queue
to nil!