This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-02-07
Channels
- # announcements (6)
- # babashka (17)
- # beginners (72)
- # calva (27)
- # cider (26)
- # circleci (6)
- # clj-kondo (35)
- # cljdoc (3)
- # clojure (22)
- # clojure-australia (2)
- # clojure-dev (45)
- # clojure-france (2)
- # clojure-italy (2)
- # clojurescript (60)
- # conjure (16)
- # cursive (8)
- # datahike (10)
- # datascript (1)
- # datomic (3)
- # emacs (5)
- # fulcro (16)
- # graalvm (4)
- # honeysql (1)
- # joker (10)
- # luminus (3)
- # malli (7)
- # off-topic (28)
- # pathom (4)
- # pedestal (2)
- # polylith (1)
- # re-frame (6)
- # reagent (9)
- # reveal (4)
- # shadow-cljs (48)
- # slack-help (1)
- # tools-deps (30)
- # vim (24)
I’m starting a new Playlist on YouTube titles “Grokking Fulcro”. This is a dual-purpose video series: • Help existing Fulcro users understand the low-level details. • Show common patterns. Fulcro does things differently than people expect, so knowing how to “think” about common problems requires some shifts that people often struggle with. • Expose people less familiar with Clojure(script) to some of the superpowers you gain by using it. First video just dropped. Here’s the playlist: https://www.youtube.com/watch?v=3dZK5seIaVI&list=PLVi9lDx-4C_TBRiHfjnjXaK2J3BIUDPnf&index=1&ab_channel=TonyKay

Are there any concrete examples of websocket push-handlers around? I’m leaning towards figuring out a way that the data provided by a push is in the same shape as a mutation with targeted return values (https://book.fulcrologic.com/#ReturnValues). Does this seem reasonable? I’d like to see what others have come up with.
In developing your push messages, include an indicator of what component (name in the UI component registry key?) should be used for merge. Then it’s just merge-component!
.
creating edges (targeting) is also something you’ll need to decide on…perhaps generalizing that to something in a UISM actor model?
then your messages could be much more generic and not tied to the UI, and the actors in the UISM could provide what you need.
https://cljdoc.org/d/com.fulcrologic/fulcro/3.1.20/api/com.fulcrologic.fulcro.ui-state-machines ?
there’s, of course, some coupling of knowing what to push from the server and having that macth UI expectations.
I think UISM is a good match, actually. There’s probably not many “states” to it, but the generalizations UISM allows for hooking in “actors” is handy.
I’ve been leaning more and more towards thinking that state machines are the end state of decoupling.