sinatra/sinatra — pull request #884 by huoxito (2014-06-14 02:18:23+00:00)
Title: Deprecate :after-handler value for show_exceptions

It's very confusing for new users as they will write custom handlers
with `error(*codes, &:block)` but those would never run in development
because `handle_exception!` was raising a general exception before
checking for custom errors.

I believe the only advantage for that would be to display stack traces
on the browser for users but I think most of the times users are catching
custom errors they don't care much about the stack trace or even if they
care they can always raise the exception again

It's been a couple months I've tried to use sinatra built in error handler but would always drop it because I thought it didn't work till today when I took a closer look. I see README mentions the `:after_handler` option but it was not clear to me at all that I had to set that in order to make my error handler run in development. Initially I thought of submitting a README change to mention that here https://github.com/sinatra/sinatra#error-handling but after reading the code decided to take a chance on dropping that config option value and hear what you guys think?

In case you have strong options against it I can submit another PR to mention about the `show_exceptions, :after_handler` value on the error-handling section.