Fork me on GitHub
#clojure-spec
<
2018-03-11
>
misha08:03:06

boy, I hope that failing to read doc from db due to validation error about extra unspecified kv – is not "the clojure way"

borkdude09:03:38

I think his argument was more about representing specs in data rather than code

ikitommi10:03:10

both open & closed specs/schemas have valid use cases. Some comments from the GraphQL world: https://github.com/facebook/graphql/issues/127

misha11:03:14

The defaults matter.

borkdude11:03:50

We have a poor man’s graphQL in which we can express *: {:a {:filter/default {:b true}}} applied to {:a {:some-key {:b 1 :c 2}}} gives you {:a {:some-key {:b 1}}}

borkdude20:03:58

As of now it’s kind of hard to relate function arguments to the specs for them. Maybe this is what the above tweet was also about: creating a different naming scheme