This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-10
Channels
- # aleph (4)
- # beginners (32)
- # cider (12)
- # cljs-dev (56)
- # cljsrn (7)
- # clojars (3)
- # clojure (165)
- # clojure-dev (33)
- # clojure-germany (1)
- # clojure-italy (27)
- # clojure-russia (7)
- # clojure-spec (24)
- # clojure-uk (62)
- # clojurescript (37)
- # core-async (7)
- # core-matrix (1)
- # cursive (9)
- # data-science (8)
- # datomic (8)
- # duct (4)
- # events (1)
- # figwheel (7)
- # flambo (3)
- # fulcro (43)
- # hoplon (25)
- # jobs-discuss (8)
- # lein-figwheel (4)
- # luminus (2)
- # off-topic (35)
- # om (8)
- # om-next (3)
- # onyx (30)
- # pedestal (62)
- # portkey (2)
- # protorepl (2)
- # re-frame (40)
- # reagent (9)
- # shadow-cljs (123)
- # specter (30)
- # sql (22)
- # testing (1)
- # uncomplicate (40)
- # unrepl (3)
- # vim (13)
- # yada (5)
hey @malcolmsparks, is it still your intention to move yada off of schema and on to spec at some point ?
When spec is out of alpha, yes. But would like to properly disentangle params from yada core in the process.
cool - i'm definitely not anxious for it to happen anytime soon - i've got a tonne of schema to port when it does happen 😬
to clarify, there's two aspects of usage of schema in yada. 1) Params, body validation, etc. 2) Resource validation 2 can go 100% spec, as it's private api (to my knowledge) 1 needs to become a more flexible api as to allow both schema, spec & anything else you can conjure up.
I'm in no rush either!