You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -160,7 +160,7 @@ The API framework is responsible for catching all exceptions thrown during an En
160
160
All endpoints that implement `Firehed\API\Interfaces\HandlesOwnErrorsInterface` (which is a part of `EndpointInterface` prior to v4.0.0) will have their `handleException()` method called with the thrown exception.
161
161
This method _may_ choose to ignore certain exception classes (by rethrowing them), but must return a PSR `ResponseInterface` when opting to handle an exception.
162
162
163
-
Starting in v3.1.0, error handling can be implemeneted globally by providing a `Firehed\API\Interfaces\ErrorHandlerInterface` to the Dispatcher via `setErrorHandler()`.
163
+
Starting in v3.1.0, error handling can be implemeneted globally by providing a `Firehed\API\Errors\HandlerInterface` to the Dispatcher via `setErrorHandler()`.
164
164
This is functionally identical to `HandlesOwnErrorInterface` described above, with the addition that the PSR `ServerRequestInterface` will also be available (primarily so that the response can be formatted appropriately for the request, e.g. based on the `Accept` header).
165
165
166
166
Finally, a global fallback handler is configured by default, which will log the exception and return a generic 500 error.
0 commit comments