This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-17
Channels
- # aleph (3)
- # announcements (12)
- # beginners (80)
- # boot (3)
- # braveandtrue (16)
- # calva (3)
- # cider (82)
- # clojure (100)
- # clojure-art (3)
- # clojure-dev (79)
- # clojure-estonia (1)
- # clojure-europe (4)
- # clojure-finland (15)
- # clojure-indonesia (1)
- # clojure-italy (20)
- # clojure-nl (4)
- # clojure-spec (24)
- # clojure-sweden (2)
- # clojure-switzerland (1)
- # clojure-uk (99)
- # clojurescript (145)
- # cursive (8)
- # data-science (7)
- # datomic (26)
- # emacs (4)
- # figwheel-main (20)
- # fulcro (8)
- # graphql (3)
- # hoplon (2)
- # jobs (1)
- # kaocha (5)
- # leiningen (2)
- # liberator (19)
- # off-topic (16)
- # pathom (9)
- # perun (1)
- # portkey (2)
- # re-frame (17)
- # reitit (1)
- # shadow-cljs (26)
- # spacemacs (7)
- # vim (49)
sorry for simple question, but couldn’t find it in readmes and it’s not working for me now - can you add the trim-v
interceptor to reg-sub
? are interceptors on reg-sub
not a thing?
@hoopes No, there's no such thing as trim-v
for subs
subs don't have interceptors
I want a throttled dispatch-later, so I can do 40 {:ms 500 :dispatch [...]}
over 200ms or so, and have a single dispatch fire 500ms after the first of them.
actually, after the last would work too. basically I want to save to local storage once the user stops typing.
(I'm writing one, but I wonder if that kind of debouncing is useful enough to go into re-frame)
also, another round of my favourite perennial question: I still want an effective way to refresh particular slices of data from my server when various views come and go.
having a big map in the router function is not great, but it mostly works.
I still feel like it should be tied to the subscription lifecycle - start polling when subscriber count goes from 0 to 1, stop when it goes back to 0.
OK, day8.re-frame.http-fx
question. I have a fx event handler returning http-xhrio
with on-success
set to :get-api-init-success
. I can confirm in Chrome that the GET request is going out and is being responded to with a 200, application/json body. However, the corresponding db event handler for :get-api-init-success
isn't firing at all. How do I debug this?
Is there a way to pass variables into the index.html file of a reframe project? I have some env variables I need to pass down into a script
@me1238 Two things I can think to check: do you have []
around :get-api-init-success
? and do you have :response-format
set to ((ajax/json-response-format {:keywords? true})
(assuming you want keywords)
@manutter51 Yes and yes. Not sure where to go from here.
Used re-frame-10x
and was able to see that on-failure
is indeed firing, due to inability to parse the JSON.
I understand effects aren't ordered, i'm curious where in the code i could see how that works? I'm not suggesting it be changed, i'm just curious as we have some ordering issues and we would like to reproduce them in order to fix them and i can't seem to reproduce them on my end 🙂