Veto\Debug\Controller\DebugExceptionController

Complexity

Total Complexity

1

Size/Duplication

Total Lines	23
Duplicated Lines	0 %

Coupling/Cohesion

Components	0
Dependencies	2

Importance

Changes	1
Bugs	0	Features	0

1 Method

Rating	Name	Duplication	Size	Complexity
A	handleExceptionAction()	0	20	1

<?php
/**
 * Veto.
 * PHP Microframework.
 *
 * @author Damien Walsh <me@damow.net>
 * @copyright Damien Walsh 2013-2014
 * @version 0.1
 * @package veto
 */
namespace Veto\Debug\Controller;

use Veto\HTTP\Request;
use Veto\HTTP\Response;
use Veto\MVC\AbstractController;

/**
 * ExceptionController
 *
 * This is the debug exception controller that will be called for any exceptions
 * from user code that make it to the kernel while the application is in Debug mode.
 *
 * You can override this by specifying a different class to be used for the
 * controller._debug_exception_handler service.
 *
 * @since 0.3.0
 */
class DebugExceptionController extends AbstractController
{
    public function handleExceptionAction(Request $request, \Exception $exception)

The parameter $request is not used and could be removed.

    {
        // The templates for showing exceptions are outside of the normal application
        // template path. It is therefore necessary to specify the path here.
        $this->get('php_template_engine')->addPath(
            __DIR__ . '/../Resources/Exception'
        );

        // Render the template
        $response = $this->get('php_template_engine')->render('TextHtml.html.php', array(
            'code' => $exception->getCode(),
            'file' => $exception->getFile(),
            'line' => $exception->getLine(),
            'trace' => $exception->getTrace(),
            'message' => $exception->getMessage(),
            'type' => get_class($exception)
        ));

        return new Response($response);
    }
}