This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-24
Channels
- # announcements (12)
- # aws (11)
- # babashka (1)
- # beginners (73)
- # cider (4)
- # clj-kondo (2)
- # cljsrn (4)
- # clojars (2)
- # clojure (68)
- # clojure-europe (8)
- # clojure-nl (5)
- # clojure-spec (6)
- # clojure-sweden (1)
- # clojure-uk (29)
- # clojurescript (41)
- # conjure (22)
- # datomic (33)
- # docker (58)
- # duct (3)
- # emacs (8)
- # events (1)
- # expound (3)
- # figwheel-main (5)
- # fulcro (33)
- # graphql (2)
- # kaocha (2)
- # lambdaisland (39)
- # leiningen (1)
- # nrepl (49)
- # nyc (1)
- # off-topic (77)
- # pathom (1)
- # re-frame (33)
- # reagent (28)
- # reitit (1)
- # rewrite-clj (2)
- # shadow-cljs (195)
- # spacemacs (1)
- # sql (60)
- # tools-deps (13)
- # vim (18)
- # xtdb (46)
How complete are you aiming this to be? Could it generate something else than spec syntax? There is work ongoing in making JSON Schema -> #malli and would like to see this for #schema too
I am doing this just to get familiar with vega
enough to implement few charts for my projects
I need to finish few combinator use cases, such as oneOf
, and see what can be done for string
spec (all the regexes, etc.), then I'll package it up as a lib. The main purpose would be to generate spec forms, and it will be up to user what to do with them: paste into file, etc. Now, I am not aiming for it to be fast, just maintainable.