This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-30
Channels
- # bangalore-clj (1)
- # beginners (23)
- # boot (1)
- # cider (23)
- # cljsjs (2)
- # cljsrn (4)
- # clojure (251)
- # clojure-dusseldorf (2)
- # clojure-gamedev (23)
- # clojure-italy (5)
- # clojure-russia (53)
- # clojure-sanfrancisco (5)
- # clojure-spec (7)
- # clojure-uk (66)
- # clojurescript (169)
- # community-development (21)
- # core-async (10)
- # cursive (15)
- # data-science (1)
- # datomic (7)
- # docker (1)
- # emacs (24)
- # events (1)
- # funcool (6)
- # hoplon (24)
- # liberator (1)
- # luminus (6)
- # lumo (62)
- # mount (7)
- # off-topic (1)
- # om (12)
- # om-next (5)
- # onyx (14)
- # overtone (2)
- # pedestal (58)
- # powderkeg (27)
- # protorepl (1)
- # re-frame (1)
- # ring-swagger (16)
- # rum (51)
- # spacemacs (25)
- # uncomplicate (7)
- # unrepl (22)
- # untangled (7)
- # yada (109)
Hi! Going meta: has anyone worked on generating (from a spec) the spec of it’s conformed data?
on a related note, I’ve been wrestling with the "entry points” to spec. Once I learned that s/conform
produces a new structure, e.g. when going through an s/or
, I switched to using s/valid?
. So what is the use case for s/conform
? It sort of works like s/explain
that produces an explanation on success too.
@alex.ter.weele my main usage of conform has been in macros to parse the body in a way that I can emit things in a much simpler way
@alex.ter.weele Producing a new, annotated data structure is really useful when your code needs to be able to branch on those or
tags.
For us (World Singles), we use conform
to process our REST API inputs (all string values) and process keywords, numbers, dates, and strings -- with annotations around ranges of values etc.
@alex.ter.weele validate AND transform