Fork me on GitHub
Alex Miller (Clojure team)03:10:59

well I would prioritize how you're going to use it as data over how to spec it - that's worth 10x more thought than how to spec it

Alex Miller (Clojure team)03:10:41

and multi-spec does not require that you use a top-level key - the dispatch function can be anything


There’s not way to change the spec for the nested ::tags map with multi-spec though.


The data definitely belongs in a nested map like above.


How about the current status about spec2? Will it replace the spec1?


@doglooksgood That is my understanding, yes. Spec 2 will probably just become clojure.spec once it moves out of alpha and Spec 1 will be left as-is.

Alex Miller (Clojure team)22:10:42

They may coexist for a while


Spec 1 will "never go away" completely because a lot of code out there depends on it, so it depends on your definition of "coexist".


(Maven Central is forever 🙂 )

Alex Miller (Clojure team)23:10:55

By coexist, I mean that core continues to support both in critical touch points (error handling, registry, doc)