This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-17
Channels
- # announcements (2)
- # aws (44)
- # beginners (96)
- # calva (10)
- # cider (7)
- # cljdoc (5)
- # cljsrn (2)
- # clojure (38)
- # clojure-dev (19)
- # clojure-europe (6)
- # clojure-italy (16)
- # clojure-nl (10)
- # clojure-norway (44)
- # clojure-spec (7)
- # clojure-uk (74)
- # clojurescript (133)
- # cloverage (1)
- # cursive (54)
- # datomic (78)
- # duct (11)
- # graalvm (5)
- # instaparse (4)
- # joker (3)
- # kaocha (5)
- # nrepl (2)
- # off-topic (10)
- # pathom (56)
- # pedestal (1)
- # reagent (7)
- # reitit (17)
- # shadow-cljs (144)
- # slack-help (2)
- # sql (35)
- # testing (5)
- # tools-deps (22)
- # vim (22)
- # xtdb (11)
You mean as a result of a user action, i.e., an on-click
event?
well the general answer, regardless, is you want the result of your ajax request to update your application state. So if you're doing a form-2 component, maybe you want to update the local state -- otherwise, you probably want to update the global state
I typically use cljs-ajax
or clj-http
if I'm doing heavy core.async
work on something and it fits in with the workflow
@goomba
>You mean as a result of a user action, i.e., an on-click
event?
Exactly. Thanks! Sorry for the not-so-detailed question.
no problem! sometimes I'll do them on component load, or on page load too
sometimes they happen on a loop in the background