This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-09-07
Channels
- # announcements (1)
- # babashka (28)
- # beginners (212)
- # calva (13)
- # clara (3)
- # clj-kondo (39)
- # cljsrn (1)
- # clojure (16)
- # clojure-australia (1)
- # clojure-europe (11)
- # clojure-nl (2)
- # clojure-spec (9)
- # clojure-uk (8)
- # clojurescript (66)
- # cloverage (3)
- # code-reviews (16)
- # cursive (12)
- # data-science (2)
- # datomic (118)
- # events (1)
- # garden (2)
- # improve-getting-started (1)
- # introduce-yourself (1)
- # jobs (4)
- # missionary (5)
- # numerical-computing (1)
- # off-topic (5)
- # pathom (3)
- # polylith (71)
- # re-frame (99)
- # reagent (17)
- # remote-jobs (5)
- # shadow-cljs (35)
- # tools-deps (5)
- # xtdb (4)
I'm getting a weird problem in Pathom 3. On running (pco/params env), it gives me {:com.wsscode.pathom3.connect.operation/optional? true}, which are not my parameters. If I run (get-in env [::pcp/graph ::pcp/source-ast :params]) I can find my actual parameters. Has anyone seen this?
how do you specify your params? In a placeholder? I don’t know if it’s your problem but if you specify the data in a placeholder (https://pathom3.wsscode.com/docs/placeholders) they will be available as resolver inputs but not as params (https://pathom3.wsscode.com/docs/resolvers#parameters) Regarding the :com.wsscode.pathom3.connect.operation/optional?, it’s a param injected when you use (pco/? on your eql keys:
(pco/? :key)
=> (:key #:com.wsscode.pathom3.connect.operation{:optional? true})harder to say without the full example