This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-18
Channels
- # aleph (1)
- # announcements (31)
- # babashka (9)
- # babashka-sci-dev (36)
- # beginners (72)
- # calva (20)
- # clj-kondo (99)
- # cljsrn (1)
- # clojure (77)
- # clojure-europe (33)
- # clojure-nl (4)
- # clojure-norway (12)
- # clojure-uk (4)
- # clojurescript (23)
- # cursive (2)
- # datascript (5)
- # events (1)
- # fulcro (3)
- # honeysql (3)
- # inf-clojure (82)
- # interop (2)
- # kaocha (10)
- # lsp (15)
- # meander (1)
- # missionary (10)
- # off-topic (22)
- # pathom (4)
- # pedestal (3)
- # polylith (20)
- # re-frame (10)
- # react (4)
- # reagent (4)
- # reitit (27)
- # ring-swagger (1)
- # shadow-cljs (34)
- # specter (3)
- # sql (1)
- # testing (5)
- # tools-deps (22)
- # vim (12)
Where can we plug in some sort of caching strategy?
Some attributes update every 10 minutes on the server side. So we need to df/load!
, but not all the time.
For the whole app? For a particular report? What behavior exactly do you want?
1. You could start a core.async go-loop or just JS setInterval
to call df/load! every 10 min
2. Or if the point is not to call df/load unnecessarily then you could modify the report's state machine and use your own df/load! impl that just returns the existing data if not expired yet or something...
Tip: my demo https://www.youtube.com/watch?v=rzK0_k5lzg4 presents a really useful technique for analyzing why expected data that you see in the client DB do not pop up in the UI at the expected place. It might be a little slow-paced but it is just 4 minutes. IMO time well invested. At least save the link and revisit it when you run into the problem of missing data 🙂 (https://blog.jakubholy.net/2020/troubleshooting-fulcro/ includes this and other tips)