Pedestal team, there is the function that takes the exception + context and returns the exception with :exception-type ... and other things that appears magically on error interceptor?

As per the doc-string of the `error-dispatch macro https://github.com/pedestal/pedestal/blob/master/interceptor/src/io/pedestal/interceptor/error.clj#L17 > Pedestal wraps all exceptions in ex-info on error, providing the following keys to match on: :execution-id, :stage, :interceptor, :exception-type

You can use that macro to create error handling interceptors

@souenzzo does that help?

https://github.com/pedestal/pedestal/blob/b7219050359f016bac77468547340c6eee20cb6e/interceptor/src/io/pedestal/interceptor/chain.clj#L32

I'm doing a unit test on the error handler (to ensure that ex-x generates response y). I wanted to see how the "context" (stage, type) is injected into the exception.

oh I see

Someone else using https://github.com/MichaelDrogalis/dire to "overwrite" transactions exceptions? They are really odd to catch