This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-01-07
Channels
- # announcements (27)
- # babashka (29)
- # beginners (280)
- # calva (34)
- # cider (4)
- # circleci (11)
- # cljfx (10)
- # cljsrn (1)
- # clojure (526)
- # clojure-dev (9)
- # clojure-europe (42)
- # clojure-finland (5)
- # clojure-losangeles (1)
- # clojure-nl (4)
- # clojure-taiwan (2)
- # clojure-uk (14)
- # clojurescript (40)
- # clr (43)
- # community-development (5)
- # css (4)
- # cursive (7)
- # duct (82)
- # events (1)
- # fulcro (72)
- # garden (44)
- # hoplon (3)
- # java (40)
- # jobs (4)
- # juxt (1)
- # luminus (53)
- # meander (13)
- # off-topic (26)
- # pathom (14)
- # pedestal (3)
- # portal (2)
- # rdf (3)
- # re-frame (54)
- # releases (10)
- # remote-jobs (3)
- # sci (74)
- # shadow-cljs (47)
- # startup-in-a-month (5)
- # testing (9)
- # tools-deps (73)
- # vim (12)
Hi, is anyone else having issues upgrading from Pathom 2.2.x to 2.3.0? I’m trying to upgrade a cljs project from 2.2.31 to 2.3.0 but keep getting the following error during compilation:
hello 🙂 I can only imagine some classpath issue, did you tried looking inside the jar to verify its contents?
I did, but everything seems fine 🤷
➜ jar tf pathom-2.3.0.jar
META-INF/MANIFEST.MF
META-INF/maven/com.wsscode/pathom/pom.xml
META-INF/leiningen/com.wsscode/pathom/project.clj
META-INF/leiningen/com.wsscode/pathom/README.md
META-INF/leiningen/com.wsscode/pathom/LICENSE
META-INF/
META-INF/maven/
META-INF/maven/com.wsscode/
META-INF/maven/com.wsscode/pathom/
META-INF/maven/com.wsscode/pathom/pom.properties
union_resolver_test.clj
com/
com/wsscode/
com/wsscode/pathom/
com/wsscode/pathom/parser.cljc
com/wsscode/pathom/merge.cljc
com/wsscode/pathom/map_db.cljc
com/wsscode/pathom/profile.cljc
com/wsscode/pathom/gen.cljc
com/wsscode/pathom/diplomat/
com/wsscode/pathom/diplomat/http/
com/wsscode/pathom/diplomat/http/fetch.cljs
com/wsscode/pathom/diplomat/http/clj_http.clj
com/wsscode/pathom/diplomat/http.cljc
com/wsscode/pathom/graphql.cljc
com/wsscode/pathom/specs/
com/wsscode/pathom/specs/ast.cljc
com/wsscode/pathom/specs/query.cljc
com/wsscode/pathom/core.cljc
com/wsscode/pathom/fulcro/
com/wsscode/pathom/fulcro/network.cljs
com/wsscode/pathom/misc.cljc
com/wsscode/pathom/test.cljc
com/wsscode/pathom/sugar.cljc
com/wsscode/pathom/trace.cljc
com/wsscode/pathom/connect.cljc
com/wsscode/pathom/connect/
com/wsscode/pathom/connect/gen.cljc
com/wsscode/pathom/connect/graphql.cljc
com/wsscode/pathom/connect/indexes.cljc
com/wsscode/pathom/connect/planner.cljc
com/wsscode/pathom/connect/test.cljc
com/wsscode/pathom/connect/foreign.cljc
com/wsscode/pathom/connect/graphql2.cljc
com/wsscode/common/
com/wsscode/common/async_cljs.cljs
com/wsscode/common/combinatorics.cljc
com/wsscode/common/async_clj.clj
com/wsscode/common/async_cljs.clj
com/wsscode/demos/
com/wsscode/demos/meta.clj
2 of my colleagues are facing the same issue, so I don’t think it is a problem with my machine. Could it be something with the way that Shuffle is configured?
I just tried to reproduce in a full setup, both on CLJ or CLJS (using Shadow), but here worked fine in both cases
I deleted the libraries to force a re-download before, but still fine
can you make a reproduction repo?
is it working on other machines you know?
I also suggest checking version of core.async, just in case
Bumping org.clojure/core.async
to the latest stable version did the trick.
Thanks a lot, man.
hello everybody, happy new year! I'm glad to announce a very long wanted feature in Pathom, now in Pathom 3 you can do resolvers with nested inputs! check latest on github, docs on nested inputs: https://pathom3.wsscode.com/docs/resolvers/#nested-inputs.
this required considerable changes, including changes in the indexes of Pathom, I'll give more details in the next blog post I'll make. for now if you are curious these were the changes involved in it: https://github.com/wilkerlucio/pathom3-docs/pull/5/files