Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix code or class name examples #7961

Merged
merged 1 commit into from
Nov 26, 2024
Merged

Fix code or class name examples #7961

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions en/development/routing.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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::
Expand Down Expand Up @@ -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()``.
Expand Down