This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-12-06
Channels
- # adventofcode (71)
- # aleph (1)
- # announcements (6)
- # aws (1)
- # babashka (27)
- # beginners (60)
- # biff (7)
- # calva (3)
- # clj-kondo (3)
- # clj-yaml (1)
- # clojure (60)
- # clojure-europe (43)
- # clojure-nl (3)
- # clojure-norway (75)
- # clojurescript (16)
- # code-reviews (7)
- # css (4)
- # cursive (47)
- # datascript (4)
- # events (5)
- # fulcro (37)
- # gratitude (5)
- # hyperfiddle (4)
- # introduce-yourself (4)
- # joyride (23)
- # juxt (4)
- # malli (4)
- # membrane (64)
- # nbb (8)
- # off-topic (12)
- # other-languages (6)
- # pathom (6)
- # polylith (9)
- # random (3)
- # rdf (66)
- # reitit (3)
- # releases (2)
- # shadow-cljs (18)
- # tree-sitter (10)
is there a way to update the resolver env in between running a mutation, and resolving the queries it is joined on? my use case is that I put an immutable DB view at the start of each pathom request, but after a mutation, i need to update that view to a newer one
that did not work, I don't see a way to modify the env for the mutation's query from the wrap-mutate function
I’ve solved this problem in pathom2 and pathom3 by passing in the DB as an immutable value wrapped in an atom (and possibly a separate DB conn if necessary for mutations) in the env. The queries should deref the db-value atom and the mutations should swap! the db-value atom after successful write with the updated DB.