New interface for handling application exceptions
New property, getter, and setter in the Paulus
class for the new ExceptionHandlerInterface
Two new exception handler classes for Paulus'
default implementation of the ExceptionHandlerInterface
Now using our RestfulExceptionHandler to handle
all exceptions in Paulus by default
Removing the old exception handling code that was
directly in the Paulus class
Our abstract controller now more properly rethrows
exceptions that it doesn't handle itself
Removing unused use statements
Reducing duplication between the two exception handlers
New interface for exception handlers that use a
response object
Abstracting out the default exception handler
implementations a bit more an giving the user more options
Moving things around and making our default response
no longer a lazy getter
New interface for error handlers
Giving Paulus the ability to handle low-level
errors using the ErrorHandlerInterface
Adding a new basic implementation of the
ErrorHandlerInterface and setting Paulus to use it
Boom. Smarter error handling
More information! Yay!
Unused use
Doc-blocks updated to be more informative and less
redundant
Whoooops. Returning what we said we'd return
Now splitting up the BasicErrorHandler and creating
a new LevelBasedErrorHandler that calls the basic error handler. That
way we won't have to reproduce the ErrorException code for other
handlers and it allows for an application to easily just ignore the
`error_reporting` directive if they so choose.