From 4c8d75f255d52273a6ef1a4f0271d8fc0a87f566 Mon Sep 17 00:00:00 2001 From: muxator Date: Thu, 1 Jan 2015 17:39:38 +0100 Subject: [PATCH] Renamed example: "Acme\BlogBundle" -> "AppBundle" In the context of this sentence, the correct fully-qualified class name for the controller seems to be AppBundle\Controller\BlogController::showAction and not Acme\BlogBundle\Controller\BlogController::showAction --- book/routing.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/routing.rst b/book/routing.rst index 631d0857b2b..57b489d2eb9 100644 --- a/book/routing.rst +++ b/book/routing.rst @@ -1169,7 +1169,7 @@ Notice that Symfony adds the string ``Controller`` to the class name (``Blog`` => ``BlogController``) and ``Action`` to the method name (``show`` => ``showAction``). You could also refer to this controller using its fully-qualified class name -and method: ``Acme\BlogBundle\Controller\BlogController::showAction``. +and method: ``AppBundle\Controller\BlogController::showAction``. But if you follow some simple conventions, the logical name is more concise and allows more flexibility.