Welcome back! In the journey to building your enterprise-ready Symfony MVC app, handling errors effectively is crucial. Proper error handling not only ensures a smoother user experience but also aids in debugging issues efficiently.

Symfony has a robust error handling mechanism by default. However, customizing error responses to suit your application's needs can provide better insights and a more user-friendly interface. In this lesson, you will learn how to create a custom ExceptionListener to handle exceptions and return a tailored JSON response.

By the end of this lesson, you will be able to implement a custom error handler in Symfony. The core of this will be a class called ExceptionListener, which listens for exceptions, catches them, and generates a custom JSON response.

Let's start by setting up the necessary directory and file structure. In your src/ directory, create a new folder called EventListener. Inside this folder, create a PHP file named ExceptionListener.php.

Here's the complete code for the ExceptionListener class:

php
Copy to clipboard
1<?php
2
3namespace App\EventListener;
4
5use Symfony\Component\HttpKernel\Event\ExceptionEvent;
6use Symfony\Component\HttpFoundation\JsonResponse;
7
8class ExceptionListener
9{
10    public function onKernelException(ExceptionEvent $event)
11    {
12        $exception = $event->getThrowable();
13        $response = new JsonResponse([
14            'error' => $exception->getMessage(),
15            'code' => $exception->getCode(),
16            'message' => 'This error was caught by our custom exception handler :D',
17        ]);
18
19        $event->setResponse($response);
20    }
21}

The onKernelException method retrieves the throwable exception and creates a JsonResponse containing the error message, code, and a custom message.

To ensure Symfony recognizes our custom exception listener, we need to configure it in services.yaml. Open the file config/services.yaml and add the following configuration:

YAML
Copy to clipboard
1services:
2    _defaults:
3        autowire: true      
4        autoconfigure: true 
5
6    App\:
7        resource: '../src/'
8        exclude:
9            - '../src/DependencyInjection/'
10            - '../src/Entity/'
11            - '../src/Kernel.php'
12    
13    # Register the ExceptionListener to handle exceptions
14    App\EventListener\ExceptionListener:
15        tags:
16            - { name: kernel.event_listener, event: kernel.exception, method: onKernelException }

The App\EventListener\ExceptionListener: line registers ExceptionListener as an event listener. The tags section specifies it to listen for kernel.exception events and to use the onKernelException method.

To test our custom exception listener, let's simulate a scenario where a client tries to access a route that doesn’t exist. This action will trigger an exception in your Symfony application. Our ExceptionListener will catch this exception and return a custom JSON response.

Here's an example of the JSON response you should see if you try to access a non-existent route:

JSON
Copy to clipboard
1{
2    "error":" No route found for \u0022GET http:\/\/localhost:3000\/non-existent-route\u0022",
3    "code": 0,
4    "message": "This error was caught by our custom exception handler :D"
5}

When an exception occurs, our ExceptionListener's onKernelException method captures the exception and generates this custom JSON response. This response will include:

• error: The error message of the exception.
• code: The error code associated with the exception.
• message: A custom message indicating that our exception handler caught the error.

In this lesson, you learned how to create and configure a custom exception handler in Symfony. Here's a recap of what we covered:

• The importance of error handling
• Setting up the ExceptionListener class
• Configuring the service in services.yaml
• Testing the custom exception handler

Now it's time to apply what you've learned through the provided practice exercises. This hands-on practice will help reinforce the concepts and techniques discussed.