This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-03
Channels
- # aws (6)
- # babashka (77)
- # beginners (102)
- # clj-kondo (24)
- # cljsrn (17)
- # clojure (40)
- # clojure-australia (15)
- # clojure-europe (50)
- # clojure-nl (4)
- # clojure-uk (4)
- # clojurescript (9)
- # conjure (2)
- # cursive (28)
- # data-science (1)
- # datomic (21)
- # events (5)
- # joker (15)
- # malli (136)
- # meander (1)
- # off-topic (25)
- # pathom (4)
- # podcasts-discuss (2)
- # portal (12)
- # portkey (1)
- # powderkeg (1)
- # practicalli (5)
- # re-frame (14)
- # reitit (3)
- # shadow-cljs (49)
- # specter (4)
- # tools-deps (4)
- # unrepl (1)
Morning folks 👋
Morning all 👋
Spent a couple hours yesterday retrofitting schema’s defn
macro to work with malli instead
Mind sharing how? Im curious because Im starting to play around with malli myself. Also, what are your thoughts on spec 2?
Putting things in a registry and needing a separate fdef, both make it harder to read things
Oh right. How did you go about instrumenting with malli? (Assuming you do)
Not specifically instrumenting. So spec has its instrument for replacing a function with a version with the fdef applied.
Schema's version is to declare it on the defn itself with some optional symbol :- type
syntax, then switch it on with a global var
There's also a switch for not allowing compilation at all, so it just adds the raw defn without any checking (basically elide asserts)
Reading schema's docs (Ive not used it before) :-
seems to be just for type hints, is that right?