Issues around body parameters

[kryptt]

Specifying both

(POST / "login" decoding(EntityDecoder.text)) |>> {p: String) => Ok("success")}

(POST / "login" decoding(ArgonautJSONDecoder)) |>> {p: Login) => Ok("success")}

in the HttpService fail with the server reporting Invalid Content-Type header

Ehen running through the swagger-ui, in both cases, the browser sent:
Content-Type: "text/*; charset=UTF-8"

[aryairani]

@kryptt Tell me more about this ArgonautJSONDecoder

[kryptt]

@refried Well, it is an object I had written previously that simply decodes a json body into the Login case class I had also written previously. The point was that both custom body decoders and an included text decoder threw exceptions.

This issue is still open because the commit f1807ac prevents the exception, but still does not generate the appropriate swagger metadata...

[aryairani]

Roger.

[bryce-anderson]

@kryptt, it seems to me that the problem described in the issue is fixed. Could you close this and open a new issue specific to the invalid swagger docs?

[kryptt]

fair enough