This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-08-11
Channels
- # babashka (3)
- # beginners (70)
- # calva (15)
- # cider (34)
- # clara (10)
- # cljsrn (2)
- # clojure (28)
- # clojure-europe (21)
- # clojure-france (1)
- # clojure-uk (17)
- # clojuredesign-podcast (4)
- # clojurescript (51)
- # cursive (21)
- # data-science (1)
- # datalog (2)
- # datascript (2)
- # datomic (10)
- # emacs (5)
- # esprit (24)
- # expound (9)
- # figwheel-main (15)
- # fulcro (31)
- # graphql (3)
- # jobs-discuss (27)
- # keechma (2)
- # luminus (2)
- # malli (2)
- # minimallist (14)
- # nrepl (1)
- # off-topic (4)
- # pathom (1)
- # pedestal (8)
- # re-frame (10)
- # reagent (5)
- # reitit (2)
- # rewrite-clj (54)
- # sci (1)
- # shadow-cljs (34)
- # spacemacs (12)
- # sql (17)
- # vim (16)
- # web-security (1)
About your PR for :transform
do you have any docs so I can read how it works? Why not something like (h/conformer (h/cat int? int?) (map inc))
@borkdude in the PR, there are some tests which are using the new transformer node via a new helper function.
I can write a doc once I go home later tonight. I myself like the new node and found a usecase in my Vrac project. I am interested to know if I should add more options in the node.
this one is an example with a data parsing
I actually took a look at that example, but didn't understand how that was useful: it has the same output as input?
because the functions are doing inverse transformations
inner model is sequence of things, from the outside it is a string
a predicate alone could not leverage an inner model