@bitsai: Thanks a lot! I will try this

@sreenath.n: actually, i'm sorry, i think i mis-spoke; based on the list of supported Schema elements on this page: https://github.com/metosin/ring-swagger

... i don't think (pred) is one of the supported Schema elements 😕

@bitsai: Hmmm.. I see. I had parked this to try it out later. Anyways, thanks again

@bitsai: @sreenath.n: Pred has very rough support, if predicate name is one of these three it works: https://github.com/metosin/ring-swagger/blob/master/src/ring/swagger/json_schema.clj#L99-L101

JSON Schema doesn't really allow describing more complex cases

But, if you know how you want to describe the predicate in JSON Schema, you can use field to manually set JSON Schema fields: https://github.com/metosin/ring-swagger/blob/master/src/ring/swagger/json_schema.clj#L32-L40

Something like (field (s/pred foobar?) {:type "string" :pattern "sdfsdf"})

@bitsai @juhoteperi : Right now I am building an api for our internal team to consume. So, we can live with the validation error messages. But, I am trying to figure out how can I use this for a much broader audience. We will need support for better error messages. I though https://github.com/metosin/ring-swagger#adding-description-to-schemas might help, but it did not 😞

Yes, we need easy way to add custom stuff to schemas, examples included.

One thing for better error messages would be not to squash errors into a string (https://github.com/metosin/ring-swagger/blob/master/src/ring/swagger/middleware.clj#L50), but to keep them as vectors, symbols and values.

https://gist.github.com/ikitommi/7927145ee263fc2974df ‘ish.