This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-29
Channels
- # announcements (35)
- # aws (40)
- # babashka (10)
- # beginners (119)
- # calva (25)
- # cider (13)
- # clj-kondo (15)
- # cljsrn (23)
- # clojure (205)
- # clojure-dev (3)
- # clojure-europe (15)
- # clojure-germany (3)
- # clojure-italy (3)
- # clojure-nl (2)
- # clojure-uk (58)
- # clojurescript (193)
- # community-development (2)
- # conjure (147)
- # core-async (49)
- # cursive (47)
- # datomic (27)
- # duct (1)
- # fulcro (19)
- # graalvm (3)
- # graphql (1)
- # helix (3)
- # hoplon (11)
- # jackdaw (1)
- # joker (1)
- # juxt (5)
- # kaocha (1)
- # keechma (3)
- # lambdaisland (6)
- # local-first-clojure (27)
- # malli (5)
- # off-topic (41)
- # rdf (27)
- # re-frame (7)
- # reagent (15)
- # reitit (5)
- # rum (11)
- # shadow-cljs (157)
- # spacemacs (18)
- # sql (4)
- # xtdb (8)
I'm looking through the Fulcro book (after going through the tutorial piece) as I love the idea of using EQL (and diving into Clojurescript) but it's not clear if the EQL queries can be filled on the client without a trip through to some server that understands EQL ... i.e., requiring some intermediary proxy service as in the REST example. It there a way to do that solely in the client cljs?
All the live examples in the book do just that
@jatkin So, the tx system is pluggable. You can use txn_processing ns as a basis for whatever you want to plug in. So, the short answer to your question is: yes. The longer answer is that such reordering is not an included feature.
but the entry point to the whole thing is one function that can be set in application setup
yeah, the existing thing is more complex than it needs to be, mostly to maintain compat with F2.
Cool. I'm interested in contributing to the project, so if I come up with something that I can make publishable I'll let you know.
yeah, let me know if you need pointers. The core of tx processing just needs to turn a transact!
into a series of optimistic actions, and network operations whose results are funneled back to the original mutation result handlers. You could make a very very simple one that processed the optimistic stuff during submission, and then submits the network stuff at the same time.
As a starting point, what kind of things are you thinking of simplifying? (nevermind :))