This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-10-21
Channels
- # announcements (3)
- # babashka (98)
- # beginners (69)
- # chlorine-clover (6)
- # cider (24)
- # cljsrn (2)
- # clojure (97)
- # clojure-australia (2)
- # clojure-berlin (6)
- # clojure-dev (57)
- # clojure-dusseldorf (4)
- # clojure-europe (19)
- # clojure-italy (5)
- # clojure-nl (10)
- # clojure-seattle (1)
- # clojure-uk (44)
- # clojuredesign-podcast (13)
- # clojurescript (45)
- # cursive (4)
- # data-science (1)
- # datomic (32)
- # emacs (7)
- # events (5)
- # fulcro (17)
- # java (12)
- # jobs (1)
- # lumo (2)
- # malli (5)
- # observability (16)
- # off-topic (1)
- # pathom (3)
- # pedestal (4)
- # rdf (14)
- # re-frame (54)
- # reagent (4)
- # releases (3)
- # remote-jobs (1)
- # reveal (55)
- # shadow-cljs (34)
- # spacemacs (14)
- # specter (9)
- # tools-deps (16)
- # xtdb (7)
Is there any way of "rewriting" the results of eql/project joins? For something like (eql/project ?website [* {:domain/_website-id [:domain/hostname]}])
I'd like the key to be something different than :domain/_website_id
Not within EQL itself, as far as I know, I'm afraid - although it has custom parameters, so we could consider a rename as a custom parameter
alright, good to know, would have to do rewrites in application code. Not the end of the world, but would be a nice features to have
In pathom, we can use something like that:
[{(:domain/_website-id {:pathom/as :website/domain})
[:domain/hostname]}]
Right - yeah, that seems straightforward enough then 🙂 I'm working on our EQL support at the moment, as it happens, will see what's involved
