This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-12-18
Channels
- # adventofcode (20)
- # aleph (25)
- # announcements (4)
- # babashka (117)
- # beginners (150)
- # calva (4)
- # cider (9)
- # clj-on-windows (2)
- # clojure (9)
- # clojure-europe (4)
- # clojure-italy (3)
- # clojuredesign-podcast (18)
- # clojurescript (16)
- # conjure (1)
- # core-async (35)
- # cursive (13)
- # datalevin (6)
- # datomic (6)
- # fulcro (8)
- # hyperfiddle (5)
- # malli (8)
- # nextjournal (4)
- # off-topic (51)
- # pathom (4)
- # reagent (21)
- # sci (14)
- # shadow-cljs (22)
- # specter (3)
- # testing (22)
- # tools-deps (8)
- # xtdb (7)
hey #xtdb users: any thoughts on how to make xtdb's history features and pathom resolvers play nice? coming up with a few ideas... I think the most promising one goes like this:
• add ring middleware to look for a query param like ?xtdb-validtime=...
(or a cookie? not sure what the best http option here might be)
• have the middleware extend the request (and therefore the pathom environment, in most pathom+ring setups) with a {:historical-db (xt/db node xtdb-validtime)}
• modify resolvers to prefer :historical-db
to :node
when it is set
would appreciate any thoughts on this approach