This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-16
Channels
- # aleph (2)
- # announcements (1)
- # beginners (162)
- # calva (16)
- # cider (37)
- # cljdoc (9)
- # cljs-dev (2)
- # cljsrn (3)
- # clojure (86)
- # clojure-dev (17)
- # clojure-europe (3)
- # clojure-houston (1)
- # clojure-italy (6)
- # clojure-nl (3)
- # clojure-spec (10)
- # clojure-uk (20)
- # clojuredesign-podcast (15)
- # clojurescript (7)
- # data-science (14)
- # datascript (1)
- # datomic (5)
- # emacs (8)
- # figwheel-main (8)
- # fulcro (25)
- # graalvm (1)
- # jobs (10)
- # jobs-discuss (4)
- # keechma (14)
- # leiningen (2)
- # off-topic (31)
- # onyx (1)
- # other-languages (4)
- # pathom (4)
- # pedestal (1)
- # re-frame (20)
- # remote-jobs (4)
- # shadow-cljs (25)
- # sql (6)
- # tools-deps (15)
- # vim (18)
- # xtdb (9)
Wilker, https://wilkerlucio.github.io/pathom/#_parsing_environment_and_the_reader “The parsing environment is simply a map that carries along data while parsing (and can be augmented as you go).” care to elaborate on “and can be augmented as you go”…as far as I know the only way to do that is by stashing an atom in there…is there some special return value for resolvers that will put extra stuff into env for the rest of the parse?
@tony.kay yes, there is a special thing you can use to augment env, sorry missing docs, I'll add in a bit and let you know
just a heads up, you can only do that when changing context (you can't change env for a sibling, and that would be a mess given pathom doesn't garantee the order in which attributes will process)
one way to change data for siblings is having an atom in the env, then you can change anyway (but risking concurrency issues)