From 5bee7d9d13934891c896a5e80124f08ae5f7bec6 Mon Sep 17 00:00:00 2001 From: Javier Eguiluz Date: Thu, 25 Oct 2018 09:50:29 +0200 Subject: [PATCH] Minor reword of AbstractController vs Controller --- controller.rst | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/controller.rst b/controller.rst index b6c5d048916..2656c26a40d 100644 --- a/controller.rst +++ b/controller.rst @@ -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.