This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-12-11
Channels
- # adventofcode (108)
- # announcements (4)
- # aws (11)
- # babashka (39)
- # beginners (199)
- # calva (12)
- # clj-kondo (17)
- # cljs-dev (1)
- # clojure (115)
- # clojure-dev (9)
- # clojure-europe (98)
- # clojure-italy (17)
- # clojure-nl (4)
- # clojure-norway (3)
- # clojure-seattle (7)
- # clojure-sweden (6)
- # clojure-switzerland (5)
- # clojure-uk (15)
- # clojurescript (41)
- # code-reviews (36)
- # conjure (7)
- # datomic (1)
- # emacs (1)
- # events (1)
- # fulcro (26)
- # graalvm (2)
- # helix (35)
- # jackdaw (2)
- # jobs (9)
- # jobs-discuss (5)
- # lambdaisland (2)
- # meander (24)
- # off-topic (80)
- # pathom (22)
- # pedestal (1)
- # portal (20)
- # re-frame (3)
- # releases (1)
- # reveal (13)
- # rewrite-clj (1)
- # shadow-cljs (8)
- # specter (5)
- # sql (4)
Another question, is it common/encouraged to have system only resolvers? I have some system states that I’m thinking could be easier to debug/dev if they were represented with resolvers but then i’d need to prevent clients from requesting them directly. One idea i’m running through is having a resolver that returns the database model and then downstream resolvers could take the database model and convert to the application model
I have resolvers that returns db schema, jvm startup data and I'm working//planning resolvers that returns my #pedestal routes and many more (use pathom as a "startup/component" system) For my API, I just filter some keys
with pathom3, what’s the correct way to set data (like a db connection) on env context?
@U066U8JQJ seems like initial data is not passed to data map argument that mutations take? For arity two, inspecting env context I do see the initial data, but not sure which way I’m supposed to be accessing it.
when create Smart Maps or EQL trigger, the first argument is the env, you should set the db connection there, same for mutations
like: (psm/smart-map (assoc env ::my-db ...) {:my.customer/id "123"})
makes sense?
so pathom-indexes/register
creates an env (not just indexes), and we can assoc additional env values into it before calling smart-map or eql process
i’m trying this
(pathom-eql/process
(assoc indexes
::ctx/conn (dc/conn))
eql))
but assoc’ed data does not seem to be included in map passed to mutationsthere are two maps, the env and params
to use env you need to declare the mutation with both
(pco/defmutation mmmm [env params])
parts of Pathom Viz integrated in Reveal