Hmm...so there is a problem with that approach too...
# ktor
m
Hmm...so there is a problem with that approach too, I think. For example, it might be that my application also throws
MissingKotlinParameterException
in some other circumstance: for example, my service might itself might call a downstream 3rd party service, and that might return some invalid JSON which causes a
MissingKotlinParameterException
, and so now my service responds with a 400 to the client when it ought to be a 500.