Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Minor reword of AbstractController vs Controller #10554

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 1 commit into from
Oct 26, 2018
Merged

Minor reword of AbstractController vs Controller #10554

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
10 changes: 6 additions & 4 deletions controller.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -147,10 +147,12 @@ and many others that you'll learn about next.
.. tip::

You can extend either ``Controller`` or ``AbstractController``. The difference
is that when you extend ``AbstractController``, you can't access services directly
via ``$this->get()`` or ``$this->container->get()``. This forces you to write
more robust code to access services. But if you *do* need direct access to the
container, using ``Controller`` is fine.
is that when you extend ``AbstractController``, you can't access to your services
via ``$this->get()`` or ``$this->container->get()``, only to a set of common
Symfony services. This forces you to write more robust code to access services.

Moreover, in Symfony 4.2 ``Controller`` was deprecated in favor of
``AbstractController``, so using the latter will make your apps future-proof.

.. versionadded:: 3.3
The ``AbstractController`` class was added in Symfony 3.3.
Expand Down