This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-29
Channels
- # announcements (4)
- # architecture (1)
- # beginners (113)
- # boot (17)
- # calva (40)
- # cider (9)
- # clara (1)
- # cljs-dev (21)
- # cljsrn (21)
- # clojure (47)
- # clojure-dev (8)
- # clojure-europe (2)
- # clojure-italy (46)
- # clojure-nl (10)
- # clojure-spec (1)
- # clojure-turkiye (1)
- # clojure-uk (46)
- # clojurescript (102)
- # core-async (21)
- # cursive (35)
- # data-science (1)
- # datomic (7)
- # emacs (2)
- # graphql (1)
- # lumo (15)
- # nrepl (4)
- # nyc (1)
- # off-topic (5)
- # overtone (3)
- # pathom (10)
- # quil (6)
- # re-frame (30)
- # reagent (7)
- # reitit (33)
- # rewrite-clj (1)
- # shadow-cljs (37)
- # spacemacs (73)
- # test-check (3)
- # testing (2)
- # vim (59)
are there any plans to support global resolver resolution in Connect mutations? I would love the automatically get :current-user/name
for logging purposes, and I already wrote a resolver for it
{::pc/input [:utc-time/now :current-user/email]
::pc/params [:arg1 :arg2]
::pc/output [:model/id]}
@thenonameguy what you mean supports global resolution? if you jsut want to run a subquery, you can call the parser from the inside, something like:
(pc/defmutation do-thing [{:keys [parser] :as env} _]
{::pc/sym 'user/do-thing}
(let [user-name (parser env [:current-user/name])]
...))
(remember to read the channel in case you are using async or parallel parsers)
@souenzzo what data you would like available as ::pc/query
?