ring-swagger & compojure-api
ikitommi 2017-10-13T05:15:15.000026Z

both the SpecCoercion and SchemaCoercion are implemented as Records, so you can print them out to see if it look ok. There could be specs out of help verifying that the data is sound after transformations.

psalaberria002 2017-10-13T12:02:17.000241Z

In case someone faces the same issue I had about strict coercion, switching to spec did the trick.

psalaberria002 2017-10-13T12:04:58.000268Z

not what I was looking after, but it works

bmabey 2017-10-13T17:19:12.000294Z

the gist was very helpful thanks!

bmabey 2017-10-13T17:21:51.000213Z

@ikitommi How are you suppose to use s/or or s/coll-of with spec-tools/compojure-api? For example, I have a route that I want to return (s/or :b ::bar :f ::foo). Using s/or doesn't seem to work with compojure-api though, only one is allowed. e.g. https://gist.github.com/bmabey/ea68b00e48f914ad3a0d4aa31c01e196

bmabey 2017-10-13T17:45:40.000084Z

I'm pretty sure this is a bug so I've opened up an issue: https://github.com/metosin/compojure-api/issues/344