This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-02-10
Channels
- # announcements (6)
- # architecture (2)
- # babashka (30)
- # beginners (90)
- # calva (21)
- # cider (22)
- # clj-kondo (27)
- # cljs-dev (7)
- # clojure (132)
- # clojure-europe (51)
- # clojure-nl (12)
- # clojure-norway (3)
- # clojure-spec (3)
- # clojure-uk (5)
- # clojurescript (69)
- # cloverage (9)
- # conjure (5)
- # core-async (54)
- # cursive (14)
- # datomic (34)
- # emacs (7)
- # fulcro (10)
- # graalvm (40)
- # graalvm-mobile (2)
- # gratitude (2)
- # improve-getting-started (1)
- # introduce-yourself (1)
- # jobs-discuss (61)
- # leiningen (5)
- # malli (6)
- # off-topic (59)
- # pathom (11)
- # polylith (38)
- # reagent (3)
- # reitit (3)
- # rewrite-clj (3)
- # shadow-cljs (53)
- # tools-build (35)
- # transit (8)
- # vim (62)
- # web-security (26)
- # xtdb (4)
Crosspost from #clojurescript because this affects fulcro-rad
: https://clojurians.slack.com/archives/C03S1L9DN/p1644487265112059
TLDR: The pom.xm
in fulcro-rad
needs an update, otherwise old dependencies are pulled in, such as cljc.java-time:0.1.17
instead of 0.1.18
.
I stumbled across this, because I updated to the latest version of CLJS which removes the global access to google modules like goog.obj
and this is a breaking change for the old version of java-time.
It's already fixed / updated in RADs deps.edn
though, but the pom takes precedence over deps for transitive deps of a projects jars.
Long story short, https://github.com/fulcrologic/fulcro-rad/pull/83
Upgraded my RAD project to Pathom3, but I see that Inspect doesn't support it yet, and to use the index explorer, a workaround would be to use Pathom Viz with its connector. Can anyone suggest how I could incorporate a call to https://github.com/wilkerlucio/pathom-viz-connector/blob/f774c1f6bb42f2bcf7363958c3805dd4aa08386c/src/com/wsscode/pathom/viz/ws_connector/pathom3.cljc#L73 when setting up the DB parser in RAD around https://github.com/fulcrologic/fulcro-rad-demo/blob/1d8b7b1bba31aca925335f35f8b1486c6a25d4a0/src/xtdb/com/example/components/parser.clj#L22?
What's the problem? If new-processor returns a parser than just call connect-env on that as in the docstring?
connect-env expects [env config] as arguments. How do I get those from the result of new-processor?
The config
is there, but the env gets built up inside new-processor
, as I understand it..
Ok. From the docstring it looks like it takes (p.connector/connect-parser {::p.connector/parser-id ::my-parser} (p/parser ...))
Perhaps #pathom can be of more help?
@tony.kay Thx for the port to Pathom3 — it’s working for me in “fulcro-rad-demo”, and I’ve written 5+ resolvers in it (including one batch resolver), and my first mutation last night! I appreciate many of the simplifications it affords. Purely FYI. cc @wilkerlucio