Skip to content

Controller naming habits #9282

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

Merged
merged 2 commits into from
Feb 18, 2018
Merged

Controller naming habits #9282

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2b61e3b
suggest(Controller): suggestion about naming habits
Guikingone Feb 16, 2018
5b29f5b
Minor reword
javiereguiluz Feb 18, 2018
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 controller.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,8 +58,8 @@ This controller is pretty straightforward:
the ``use`` keyword imports the ``Response`` class, which the controller
must return.

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

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