route(..).throws(...) eats stack trace

Hey, project is really cool, just starting to dig into it… leaps and bounds better than my original plan of having to do hand rolled annotation + processing. One issue I’m running into is that it seems that

apiRouting {
  route("/example").throws(exampleError)

will eat the underlying stack trace, and simply output something similar to

ktor.application - 500 Internal Server Error: POST - /example 

Obvious this isn’t ideal for a variety of reasons 😄

[Wicpar]

It actually works properly, the throws catches the exception and handles it as a response as it is no longer considered an error. You can print it in the handler if you need to, there is a parameter that accepts a transform function in apiException

[unredundant]

Oh I had forgotten about this ticket, I’m going to close it since this is expected behavior