Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 2e76707

Browse filesBrowse files
committed
minor #9282 Controller naming habits (Guikingone, javiereguiluz)
This PR was merged into the 4.0 branch. Discussion ---------- Controller naming habits As Symfony isn't an `MVC` framework but a `Request/Response` one (see #8153 (comment)), the name of the class which handles the Request isn't forced to contain `Controller`, it's probably more a common usage than a need to make Symfony works. Commits ------- 5b29f5b Minor reword 2b61e3b suggest(Controller): suggestion about naming habits
2 parents 50911a3 + 5b29f5b commit 2e76707
Copy full SHA for 2e76707

File tree

Expand file treeCollapse file tree

1 file changed

+2
-2
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+2
-2
lines changed

‎controller.rst

Copy file name to clipboardExpand all lines: controller.rst
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,8 +58,8 @@ This controller is pretty straightforward:
5858
the ``use`` keyword imports the ``Response`` class, which the controller
5959
must return.
6060

61-
* *line 7*: The class can technically be called anything - but should end in the
62-
word ``Controller``
61+
* *line 7*: The class can technically be called anything, but it's suffixed
62+
with ``Controller`` by convention.
6363

6464
* *line 12*: The action method is allowed to have a ``$max`` argument thanks to the
6565
``{max}`` :doc:`wildcard in the route </routing>`.

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.