This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-24
Channels
- # announcements (8)
- # aws (12)
- # babashka (84)
- # beginners (380)
- # calva (56)
- # clj-kondo (52)
- # cljdoc (4)
- # cljs-dev (327)
- # cljsrn (4)
- # clojure (154)
- # clojure-italy (5)
- # clojure-nl (3)
- # clojure-uk (21)
- # clojurescript (52)
- # conjure (133)
- # cursive (64)
- # datomic (33)
- # emacs (22)
- # fulcro (35)
- # graalvm (24)
- # graphql (1)
- # kaocha (1)
- # leiningen (1)
- # off-topic (24)
- # onyx (2)
- # pathom (10)
- # re-frame (3)
- # reagent (3)
- # reitit (3)
- # shadow-cljs (48)
- # spacemacs (12)
- # tools-deps (98)
- # xtdb (7)
hello, wanted to say that we have been evaluating pathom last few days and we are blown away. Serioulsy good job @wilkerlucio
Hello! I struggle translating a working GraphQL query into Pathom Connect + graphql. I have described my problems here https://github.com/wilkerlucio/pathom/issues/155 and would appreciate any help. Thank you!!!
thanks for the great report, I'll have some time to look into it later today
Thanks a lot! I plan to add a little more high level tests for the GraphQL PC that could also serve as a documentation (query + index -> resolver -> driver that returns hard-coded response -> errors and data). The current unit tests are too low for that.
@wilkerlucio Could you perhaps be so kind and show me how to write such a high-level/integration style? I see I know too little to be able to pull it off. Something like running
(parser
{::pc/indexes <based on graphql2-test/indexes>
::pcg/prefix "service"
::pcg/ident-map {...}
::p.http/driver (fn [r] (verify-expected-query r)
"{\"data\":{...}}")}
[{[:service.Customer/id "123"]
[:service.Customer/cpf]}]
? I guess that graphql2-test/query-env
quite close to the env I need, I would perhaps just need to plug into the env the actual com.wsscode.pathom.connect.graphql2/graphql-resolve
🙏for the integrations like these, I want to warn you they are about to change, I plan to release this weekend some of the new stuff, and sadly the graphql integration will need rework (graphql3 is coming 😛, but probably not this weekend), so I like to write about those integrations for this new scenario, since this is the thing moving forward