Hi I still struggle with input payload validation/...

# http4k

[Nicola]

Hi I still struggle with input payload validation/deserialization .. with plain httphandler I am able to get decent error messages (eg "Invalid JSON Could not resolve type id '896' as a subtype of `it.multidialogo.payment_order_printer.domain.Payment"), when switching to contract route I am back to a message like this:
{"message":"Missing/invalid parameters","params":[{"name":"body","type":"body","datatype":"object","required":true,"reason":"Invalid"}]}
I've tried to read sources of bindContract but it's not easy to me to understand where deserialization is taken place ..

[dave]

If you override the error response renderer you should be able to get at the exact stacktrace

[Nicola]

"error response handler" ? Ok I'll search for it htanks a lot