This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-12
Channels
- # bangalore-clj (1)
- # beginners (28)
- # boot (33)
- # chestnut (3)
- # cider (35)
- # cljs-dev (64)
- # cljsrn (16)
- # clojure (95)
- # clojure-android (6)
- # clojure-austin (1)
- # clojure-italy (5)
- # clojure-korea (1)
- # clojure-russia (55)
- # clojure-sg (1)
- # clojure-spec (25)
- # clojure-uk (57)
- # clojurescript (120)
- # code-reviews (7)
- # community-development (2)
- # core-async (3)
- # cursive (6)
- # data-science (3)
- # datascript (10)
- # datomic (12)
- # devcards (1)
- # emacs (9)
- # gsoc (7)
- # hoplon (18)
- # lumo (2)
- # off-topic (10)
- # om (24)
- # onyx (17)
- # pedestal (46)
- # powderkeg (1)
- # protorepl (7)
- # re-frame (31)
- # ring-swagger (34)
- # spacemacs (10)
- # specter (9)
- # sql (39)
- # unrepl (9)
- # untangled (3)
- # utah-clojurians (1)
@macalimlim I would have thought the re-frame docs themselves would have been a good place to start
All organised ina tutorial style
Are there any demos about how to do polling ajax(control repeatedly make a same ajax request) with re-frame? Thanks.
use dispatch-later
?
The simple example updates the clock every 1 second
--------------------------- WARNING --------------------------- The re-frame-template has encouraged use of this construct:
(def debug?
^boolean js/goog.DEBUG)
The idea being that one could use debug?
to trigger Dead Code Elimination (DCE) in :advanced
builds
But a bug in recent version of CLJS means this code doesn't work. So you need to make a subtle adjustment:
(def debug?
^boolean goog.DEBUG) ;; remove the leading js/
David Nolen just reduced the bug to "minor" importance, so it probably won't get fixed any time soon, if ever: https://dev.clojure.org/jira/browse/CLJS-2023
The template itself has been updated BUT if you have already generated a project from it, you'll have to manually update the generated code.
Just used :async-flow for the first time. Loved it.
Thanks again @mikethompson
My use case wasn't for boostrapping.
I had a event handler which needed to fetch various bits of data before it could do some processing. :async-flow gave me a simple state machine style way of coordiating those activities.
@olivergeorge ah, thanks. Always good to get successful feedback. I've always felt async-flow
should have been useful to lots of people.
🙂 Preparing data for handlers seems like a good use case to me.
It's too early for any serious feedback but two things felt kind of odd - not that I see better solutions. 1) needing unique event-ids for the state machine steps, 2) passing data between the handlers involved.
1) wasn't a problem this time but feels like it could be
2) made me wonder if some complementary cofx might be helpful.
e.g. do two AJAX GETs and use them in handler.
the only way to pass the data is putting it in app-db but it's kind of private data so that feels odd.
Hello! I am looking for a way to register an unhandled error handler in re-frame or reagent. The idea is that when any unhandled error occurs, a user friendly message is displayed. is there a standard way of doing this? Thanks!
Maybe interceptors
@antonmos ?
https://github.com/Day8/re-frame/blob/master/docs/Interceptors.md
unfortunately, i am not seeing anything related to how errors play into interceptor execution
ah, apparently this is work in progress https://github.com/Day8/re-frame/pull/330