This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-05
Channels
- # announcements (23)
- # babashka (23)
- # beginners (48)
- # calva (41)
- # clj-kondo (41)
- # cljs-dev (75)
- # cljsrn (5)
- # clojure (85)
- # clojure-europe (46)
- # clojure-nl (2)
- # clojure-spec (70)
- # clojure-uk (4)
- # clojurescript (52)
- # core-async (2)
- # cursive (16)
- # datahike (2)
- # datomic (4)
- # emacs (15)
- # figwheel-main (2)
- # fulcro (5)
- # gratitude (5)
- # helix (14)
- # introduce-yourself (2)
- # jackdaw (13)
- # keyboards (2)
- # lsp (8)
- # luminus (5)
- # malli (3)
- # meander (12)
- # nextjournal (52)
- # off-topic (19)
- # other-languages (1)
- # overtone (3)
- # pathom (4)
- # podcasts-discuss (1)
- # re-frame (6)
- # reitit (1)
- # releases (2)
- # ring (3)
- # sci (22)
- # shadow-cljs (3)
- # specter (1)
- # testing (3)
- # tools-deps (100)
- # uncomplicate (2)
Hey all, has anyone ever run into “recursive union” queries? I’ve been playing with pyramid
which has some EQL support and documented https://github.com/lilactown/pyramid/issues/13, but then realized it is likely a more general EQL problem. How would one handle this in pathom for example?
It seems that both pyramid and pathom’s recursive primitive, namely the '...
symbol, assume that the direct parent is the target of that recursion. Is there any way to say that, for example, the grandparent is the target of recursion?
Okay I actually just https://github.com/lilactown/pyramid/issues/13#issuecomment-962179903 😅 I was reaching for a union query unnecessarily. Namespaced keywords let one just ask for everything at the root, and then the parent is indeed the proper recursion target.
