From d5592ddbd71c69760bf430e097cedfcc95be74c7 Mon Sep 17 00:00:00 2001 From: Mark Scherer Date: Tue, 26 Nov 2024 16:33:28 +0100 Subject: [PATCH] Fix code or class name examples --- en/development/routing.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/en/development/routing.rst b/en/development/routing.rst index c8100e2e08..2dda7673b2 100644 --- a/en/development/routing.rst +++ b/en/development/routing.rst @@ -712,7 +712,7 @@ When using nesting, you need to chain them together:: ['prefix' => 'Admin/MyPrefix', 'controller' => 'TodoItems', 'action' => 'create'] ); -This would link to a controller with the namespace ``App\\Controller\\Admin\\MyPrefix`` and the file path +This would link to a controller with the namespace ``App\Controller\Admin\MyPrefix`` and the file path ``src/Controller/Admin/MyPrefix/TodoItemsController.php``. .. note:: @@ -1579,7 +1579,7 @@ Custom Route Classes Custom route classes allow you to extend and change how individual routes parse requests and handle reverse routing. Route classes have a few conventions: -* Route classes are expected to be found in the ``Routing\\Route`` namespace of +* Route classes are expected to be found in the ``Routing\Route`` namespace of your application or plugin. * Route classes should extend :php:class:`\\Cake\\Routing\\Route\\Route`. * Route classes should implement one or both of ``match()`` and/or ``parse()``.