This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-05
Channels
- # announcements (7)
- # babashka (61)
- # beginners (146)
- # cider (4)
- # clj-kondo (25)
- # cljsrn (29)
- # clojars (30)
- # clojure (30)
- # clojure-australia (17)
- # clojure-europe (43)
- # clojure-italy (16)
- # clojure-nl (2)
- # clojure-spec (13)
- # clojure-sweden (7)
- # clojure-uk (8)
- # clojurescript (38)
- # cursive (12)
- # datomic (42)
- # defnpodcast (2)
- # dirac (1)
- # events (5)
- # fulcro (5)
- # graalvm (43)
- # graphql (11)
- # helix (6)
- # jackdaw (13)
- # jobs (4)
- # lambdaisland (8)
- # malli (12)
- # off-topic (83)
- # pathom (9)
- # podcasts-discuss (2)
- # re-frame (6)
- # reagent (3)
- # reitit (8)
- # remote-jobs (1)
- # shadow-cljs (40)
- # vim (21)
For a new project, use spec or spec2? If I go with spec, will it be obsoleted sometime?
I recently got into malli - https://github.com/metosin/malli can highly recommend if you're looking to invest in something - it's also quite simple to generate clojure.spec.alpha or clojure.alpha.spec forms from malli schemas if you ever do want to switch
It seems unlikely that spec2 will obsolete spec1 in 2021.
spec2 will not cause spec1 to change its behavior.
spec 2 is not ready for use yet, so spec
when spec 2 is ready, it will include help for migrating to it
@alexmiller Since this seems to be a “Frequently Asked Question” about Spec 2, maybe you could put a big bold notice on the repo that says “EXPERIMENTAL: DO NOT USE YET!” or something? 🙂
It says "This library is a work in progress provided to gather feedback during development." and there are no releases of it so....
yeah but "v2 not ready yet" doesn't alleviate people's concerns about whether they should invest in spec 1
spec 1 is a thing, feel free to use it
the spec language between the two is substantially the same. part of releasing spec 2 will be providing a migration path from spec 1