This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-05
Channels
- # announcements (17)
- # aws (1)
- # babashka (68)
- # beginners (88)
- # calva (85)
- # chlorine-clover (10)
- # cider (5)
- # cljsrn (4)
- # clojure (99)
- # clojure-android (1)
- # clojure-denmark (1)
- # clojure-europe (15)
- # clojure-italy (5)
- # clojure-nl (3)
- # clojure-spec (1)
- # clojure-uk (67)
- # clojurescript (44)
- # core-async (44)
- # cryogen (4)
- # cursive (22)
- # data-science (2)
- # datascript (10)
- # datomic (29)
- # duct (11)
- # editors (2)
- # emacs (2)
- # events (1)
- # fulcro (28)
- # ghostwheel (7)
- # graalvm (8)
- # instaparse (6)
- # java (34)
- # jobs (9)
- # jobs-discuss (71)
- # juxt (12)
- # luminus (3)
- # malli (15)
- # meander (9)
- # nrepl (4)
- # off-topic (44)
- # pathom (13)
- # reagent (22)
- # schema (1)
- # shadow-cljs (39)
- # spacemacs (2)
- # test-check (1)
- # tree-sitter (5)
- # xtdb (5)
- # yada (1)
is there a recommended pattern to fallback on a remote parser when a local parser didn't find all keys? should it be a mega resolver or a last reader?
@yenda that's whats coming on the next version 🙂 I have two projects using a setup in the way you described, they have both local parsers (running on CLJS) and remote parsers (running on some server), for basic cases it already works, but I still have to document a lot of it, and I'm still working on some tooling, so until I have docs and tools I dont recommend it for general usage. but if you are feeling adventurous, there are examples in the tests: https://github.com/wilkerlucio/pathom/blob/query-planner/test/com/wsscode/pathom/connect/planner_readers_test.cljc#L328-L562 (use the alpha releases to have it available)
I also like to improve the visibility of the work I'm doing, because that's been a quite long work process to get this out, and I like to provide something so people that want to follow can know whats going on, not going deep on this now, but expect some news around that soon 🙂

@wilkerlucio that look awesome! In my case I have a pretty simple use case because I only have one remote and I know that whatever isn't solved locally will be solved remotely, so I was basically looking for a solution to send the remainers of the query that have not been solved to the remote
but maybe it isn't that simple, I was hoping there would be a way to get the remaining query after the local parser ran and just send it to the remote parser
this can be done with some map manipulation code, get the query, query the data, make a diff and run, I guess its a simpler problem
depends on the case, are you doing it in a fulcro app?