@slipset pushed spec-tools 0.9.1 with the visitable
st/merge (added also to json-schema), thanks!
Well, thank you!
Should I create an issue for the
merge case I mentioned above?
I didn’t manage to narrow it down super easily, but could spend some time doing that if it’s interesting for you.
I might also outline why I’m doing this:
Our entities, if you will, have a spec for their fields eg
(s/def ::foo (s/keys :req-un [:name :description]))
This is what you’d need to send to the api in order to create a
foo. The api however returns this with some metadata, so the return has more fields than the input.
Also, there is a difference in the spec for wether it’s a create or an update. a create only contains
:field as above, but the update also needs an
My idea was then to generate these additional specs based on the spec for
foo which only contained the user supplied fields,
Does this make sense?