This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-22
Channels
- # alda (2)
- # announcements (1)
- # babashka (32)
- # beginners (67)
- # calva (1)
- # cider (19)
- # clerk (11)
- # clj-commons (35)
- # clj-kondo (7)
- # cljsrn (2)
- # clojure (35)
- # clojure-europe (86)
- # clojure-nl (5)
- # clojure-norway (5)
- # clojure-russia (6)
- # clojurescript (16)
- # clr (21)
- # conjure (1)
- # core-async (10)
- # cryogen (1)
- # cursive (12)
- # data-science (1)
- # emacs (29)
- # events (4)
- # figwheel-main (2)
- # graalvm (9)
- # gratitude (7)
- # honeysql (4)
- # hugsql (3)
- # hyperfiddle (23)
- # jobs (1)
- # jobs-discuss (4)
- # joyride (9)
- # malli (2)
- # off-topic (81)
- # portal (7)
- # reagent (19)
- # reitit (1)
- # releases (4)
- # shadow-cljs (121)
- # xtdb (3)
is there a version of ^::clerk/sync
that forces re-rendering in the browser when the atom is changed in the JVM?
I think that is supposed to happen already
could be a regression
I’m trying this example and it looks like the call to clerk/recompute!
is necessary to make it update
No actually it’s not!
it should be updating the reagent atom on the client side whenever the server side changes
💯 2
so any reagent component in a viewer where you deref
the synced atom should update
thanks for confirming the intended behaviour, I think I’m misusing it somehow, but it’s still unclear how 🙂
can you perhaps provide a repro?
narrowing down a bit…