This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-19
Channels
- # announcements (5)
- # asami (7)
- # aws (10)
- # babashka (10)
- # beginners (49)
- # calva (12)
- # cider (5)
- # circleci (1)
- # clj-kondo (25)
- # clj-yaml (14)
- # clojars (5)
- # clojure (134)
- # clojure-europe (142)
- # clojure-france (3)
- # clojure-nl (1)
- # clojure-norway (4)
- # clojurescript (10)
- # cursive (8)
- # datomic (19)
- # emacs (11)
- # fulcro (8)
- # graalvm (29)
- # honeysql (7)
- # jobs (4)
- # jobs-discuss (9)
- # lsp (196)
- # obb (4)
- # off-topic (40)
- # pathom (4)
- # releases (4)
- # remote-jobs (3)
- # shadow-cljs (16)
- # sql (25)
- # squint (2)
- # tools-deps (12)
- # xtdb (7)
- # yada (4)
This is probably too ambiguous a question, but, I'm using the Datomic dynamic resolver and pbip/mutation-resolve-params and it will resolve nested ::pco/params for a mutation, but not for a resolver. I.e., if the top-level key in the params doesn't return one of the nested attributes, the Datomic dynamic resolver finds them, but only for mutations.e
unrelated, what is the "datomic-source" arg supposed to be? https://github.com/wilkerlucio/pathom3-datomic/blob/main/src/main/com/wsscode/pathom3/connect/datomic.clj#L193
pathom3-datomic's compute-dynamic-nested-requirements doesn't work with optional input (e.g., (pco/? :some/thing)
as a result I've switched to using a mutation for compiling "reports" and resolved params