eonx-com/easy-error-handler

Provides customizable ready-to-use error handler for applications

6.4.0 2024-11-20 09:57 UTC

Requires

• php: ^8.2
• eonx-com/easy-logging: ^6.4
• eonx-com/easy-utils: ^6.4
• nesbot/carbon: ^3.7
• nikic/php-parser: ^5.0
• symfony/config: ^7.1
• symfony/console: ^7.1
• symfony/dependency-injection: ^7.1
• symfony/error-handler: ^7.1
• symfony/finder: ^7.1
• symfony/http-foundation: ^7.1.7
• symfony/http-kernel: ^7.1
• symfony/property-access: ^7.1
• symfony/serializer: ^7.1
• symfony/service-contracts: ^3.5
• symfony/translation: ^7.1

Requires (Dev)

• eonx-com/easy-bugsnag: ^6.4
• eonx-com/easy-test: ^6.4
• eonx-com/easy-webhook: ^6.4
• laravel/lumen-framework: ^11.0
• phpunit/phpunit: ^10.2
• symfony/framework-bundle: ^7.1

Suggests

• api-platform/core: To use ApiPlatform integration
• eonx-com/easy-bugsnag: To use EasyBugsnag integration
• eonx-com/easy-webhook: To use EasyWebhook integration
• symfony/messenger: To use Symfony Messenger integration
• symfony/validator: To use ApiPlatform integration

MIT

README

---eonx_docs--- title: Introduction weight: 0 ---eonx_docs---

Introduction

The EasyErrorHandler package allows you to easily build informative HTTP responses and reports in response to exceptions in your applications.

Using the EasyErrorHandler package, you can:

• Define a common structure for exceptions
• Generate consistent error responses for unhandled exceptions within your code
• Report exceptions to the main logging channel of your application (by default) or to custom destinations
• Automatically notify Bugsnag based on the log level of the exception (by default, if used with easy-bugsnag)

Usage overview

The package will work with any PHP exception, but it provides several tailored Exceptions for common error conditions, e.g. 404 Not Found errors.

The ErrorHandler provides the main methods to build HTTP responses for exceptions and to report on exceptions (e.g. logging).

HTTP responses are built with error response builders. These builders progressively build the response body, status code and headers. You can implement your own error response builders. The HTTP response body is formatted as JSON by default, but you can implement your own formatter (see Response format).

Error reporters report on exceptions. The default error reporter logs to the main logging channel of your application, but you can implement custom error reporters, e.g. to send email.