Out of curiosity: yada is using Prismatic Schema... 1/ how to handle custom predicates (if possible at all)? For example, if I want to make sure something is a valid UUID, I have a function valid-uuid?. However, using this function:

error converting to swagger schema [:message predicate$valid_uuid_QMARK_@7e7f769]

@kurt-yagram there is the s/Uuid and you can use custom predicates with s/constrained, like (s/constrained s/Str valid-uuid?). Ring-swagger grabs the type from the first argument (rules here: https://github.com/metosin/ring-swagger#out-of-the-box-supported-schema-elements). Related - there is a open clojure hacking session here in Finland tomorrow, one goal is to get the spec->json-schema finalized & spec runtime coercions to work properly. Will be pushed to ring-swagger.

cool!

Hi @kurt-yagram - I've had a similar issue recently wanting a parameter to be a (base64) string for json, but binary data for multipart/form-data.

2. Yes, the plan is to adopt clojure.spec quite soon. Ring-swagger is already well on the way, which is where yada gets much of its swagger support from.

That's wicket-awesome. Thx @ikitommi @malcolmsparks .

How to return custom headers with yada/resource?

Is that the right/recommended way to add headers?

yes

Is it possible to define a set of values that are valid in swagger? I mean, I tried something like: {:parameters {:path {:par #{"val1", "val2"}}}, hoping that in swagger, I would get a dropdown list of values. This doesn't seem to work, though...

Is it possible to update a running Yada listener with new routes?

It's possible, but you'd have to write your own dynamic equivalent of bidi's find-handler

I'll take a look into that. Thanks!

@kurt-yagram try s/enum

🙂

cool, that does the trick

hey guys, there is some internal yada error it seems that it renders a 500 error if you send any Accept-Charset header at all

it can be reproduced by issueing curl -gv '' -H 'Accept-Charset: utf-8’

since we don't do anything special with charsets (other than telling yada we accept /), does this hint at an actual bug in yada ?

looking at the exception, it looks like it tries to coerce something into UTF8 that returns nil, and tries to coerce that into json?

Yes, it looks like a bug.

Sorry for the poor response, I've been at a conference all day