This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-14
Channels
- # beginners (110)
- # boot (50)
- # cider (29)
- # cljs-dev (80)
- # cljsrn (10)
- # clojure (54)
- # clojure-italy (3)
- # clojure-korea (24)
- # clojure-russia (50)
- # clojure-spec (12)
- # clojure-taiwan (1)
- # clojure-uk (67)
- # clojurebridge (14)
- # clojurescript (118)
- # component (3)
- # cursive (11)
- # datomic (28)
- # dirac (31)
- # emacs (45)
- # flambo (2)
- # hoplon (53)
- # immutant (3)
- # jobs (5)
- # mount (8)
- # off-topic (10)
- # om (5)
- # onyx (52)
- # other-languages (2)
- # parinfer (1)
- # pedestal (1)
- # proton (39)
- # protorepl (2)
- # re-frame (22)
- # remote-jobs (1)
- # ring (13)
- # ring-swagger (2)
- # test-check (9)
- # untangled (28)
- # vim (12)
When creating custom Specs, what are the rules for describe*
? eval’ing it should return the Spec?
Could the describe*
of Specs be used as a serialization format over the wire (sending specs over Transit etc.)?
You should call s/form
That is intended to be a form that can serialized a wire (all symbols should be resolved etc)
There are a number of known bugs and patches on it that I have been working through so it's not 100% yet
s/form uses describe* internally but you shouldn't call that directly
thanks @alexmiller and great to hear the serialization support in the scope of spec!
I wrote some code the other day that uses s/form to traverse specs and generates a json schema from the spec, it was way cool