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)
When throwing exception created with ex-info from server, any easier way to get the error map in client side? I am now reading the error from response body in error-action, it's very verbose
You can plug in your own result handler at the global level, or change the response middleware
If my backend resolver requires more than one parameters, for example, ::pc/input #{:s1/id :s2/id}
, how should i declare my component in frontend? I could not find the relevant documentation.
I managed to get the results by including the id in the results from the parent query, {:node/list (mapv (fn [id] {:s2/id id :s1/id s1-id}) (get-list-by-s1-id s1-id))}
you could pass additional params during loading by using :pathom/context
param:
(df/load! app [:input/a "aaa"] Output {:params {:pathom/context {:input/b "BBB"}}})
https://blog.wsscode.com/pathom/v2/pathom/2.2.0/connect/resolvers.html#_multiple_inputs