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
My module custom error handler code is no longer functioning.
I’ve attempted to return to the old style that had a error handler class as each of my modules handle their own errors and I don’t want to have all the error code in the base code but contained in the module.
Here is how I have done this.
In my base AppServiceProvider I have added this to the register function
use App\Exceptions\Handler;
use Illuminate\Contracts\Debug\ExceptionHandler as ExceptionHandlerContract;
class AppServiceProvider extends ServiceProvider
{
public function register(): void
{
$this->app->singleton(ExceptionHandlerContract::class, Handler::class);
}
}
And commented out the withExceptions on the app.php file. The base handler has the code to load the module error handler code.
This works in the browser and my module exceptions are running, but when using console commands I get an error message,
[Illuminate\Contracts\Debug\ExceptionHandler] is not instantiable.
I’m not sure if this is a bug or not, or who’s it would be.
Is there a way to implement module based error handling?
The text was updated successfully, but these errors were encountered:
I am using Laravel 11.9.2 and nwidart/laravel-modules version 11.0.1.
With the change to how exceptions are handled, ie…
My module custom error handler code is no longer functioning.
I’ve attempted to return to the old style that had a error handler class as each of my modules handle their own errors and I don’t want to have all the error code in the base code but contained in the module.
Here is how I have done this.
In my base AppServiceProvider I have added this to the register function
And commented out the withExceptions on the app.php file. The base handler has the code to load the module error handler code.
This works in the browser and my module exceptions are running, but when using console commands I get an error message,
I’m not sure if this is a bug or not, or who’s it would be.
Is there a way to implement module based error handling?
The text was updated successfully, but these errors were encountered: