This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-07-10
Channels
- # admin-announcements (4)
- # beginners (21)
- # boot (85)
- # cider (31)
- # clojure (45)
- # clojure-australia (1)
- # clojure-berlin (2)
- # clojure-dev (7)
- # clojure-italy (10)
- # clojure-japan (17)
- # clojure-norway (8)
- # clojure-russia (2)
- # clojure-uk (15)
- # clojurebridge (1)
- # clojurescript (115)
- # code-reviews (13)
- # core-async (1)
- # editors (17)
- # euroclojure (5)
- # jobs (1)
- # ldnclj (9)
- # off-topic (5)
- # om (18)
- # re-frame (15)
- # reagent (25)
- # sydney (1)
Probably @surreal.analysis , I’ll put in a patch.
A common pattern that I am seeing is having two handlers: :some-feature/make-request!
with a go-routine that triggers a web request, a handler like :some-feature/response
to swap out the response and a subscription or two to provide the loading toggle and response, e.g. :some-feature/loading?
and :some-feature/response
. Feels like the job for a macro, but it's tricky to choose a good convention and I don't want to clobber other handler keywords. Has anyone investigated this?
...pretty much as described in https://github.com/Day8/re-frame/wiki/Talking-To-Servers
@estsauver not using sente yet.
to see if say the value “Log in” is somewhere in the generated hiccup, is there a nice way of doing that?
I’m thinking about using https://github.com/davidsantiago/hickory to query the result
but thought I would ask if any of you all have experience with testing reagent thigns?
I haven't used it, but perhaps https://github.com/nathanmarz/specter might be what you're after?