This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-10
Channels
- # announcements (2)
- # babashka (15)
- # beginners (174)
- # calva (16)
- # chlorine-clover (10)
- # clara (7)
- # clj-kondo (27)
- # cljdoc (10)
- # clojars (4)
- # clojure (50)
- # clojure-europe (10)
- # clojure-gamedev (3)
- # clojure-greece (1)
- # clojure-italy (4)
- # clojure-losangeles (1)
- # clojure-nl (16)
- # clojure-sg (1)
- # clojure-spec (7)
- # clojure-uk (41)
- # clojurescript (22)
- # data-science (15)
- # datascript (38)
- # datomic (2)
- # duct (15)
- # emacs (2)
- # fulcro (110)
- # funcool (9)
- # graphql (10)
- # jackdaw (8)
- # jobs (23)
- # joker (1)
- # leiningen (15)
- # luminus (1)
- # malli (20)
- # off-topic (26)
- # pathom (5)
- # pedestal (1)
- # reitit (19)
- # shadow-cljs (78)
- # spacemacs (2)
- # sql (52)
- # tools-deps (99)
- # vim (13)
@hoppy async/await stuff is gone becuase it gives more complexity that the real value. Right now with, p/let
p/plet
and p/loop
and p/recur
is more than enough for build a very complex logic without the need of the general purpose async/await
on the JS land you cant retrieve synchronously the value of promise. it is a design decision, promesa can't do nothing here
I would also suggest that you get a bit more aggressive with documenting what can't be used in cljs.
I also note that @jeaye has a blog post https://blog.jeaye.com/2017/09/30/clojurescript-promesa/ about how to use promesa in clojurescript and he's on defn podcast this round - he is using the old-style api, so that might get confusing
@hoppy If you'd like to update the code for that post to use the latest version of promesa, that'd be awesome.
I haven't used promesa (or any async/await pattern in CLJS) since 2017, when that was written.