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 3eb14aa

Browse filesBrowse files
wouterjwouterj
committed
minor #4727 Renamed example: "Acme\BlogBundle" -> "AppBundle" (muxator)
This PR was merged into the 2.6 branch. Discussion ---------- 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 ``` Commits ------- 4c8d75f Renamed example: "Acme\BlogBundle" -> "AppBundle"
2 parents caa2be6 + 4c8d75f commit 3eb14aa
Copy full SHA for 3eb14aa

File tree

Expand file treeCollapse file tree

1 file changed

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

1 file changed

+1
-1
lines changed

‎book/routing.rst

Copy file name to clipboardExpand all lines: book/routing.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1169,7 +1169,7 @@ Notice that Symfony adds the string ``Controller`` to the class name (``Blog``
11691169
=> ``BlogController``) and ``Action`` to the method name (``show`` => ``showAction``).
11701170

11711171
You could also refer to this controller using its fully-qualified class name
1172-
and method: ``Acme\BlogBundle\Controller\BlogController::showAction``.
1172+
and method: ``AppBundle\Controller\BlogController::showAction``.
11731173
But if you follow some simple conventions, the logical name is more concise
11741174
and allows more flexibility.
11751175

0 commit comments

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