From 78fcf0abad39f889012e76e12ef5fea064d04911 Mon Sep 17 00:00:00 2001 From: Thomas Landauer Date: Wed, 26 Jul 2017 19:24:05 +0200 Subject: [PATCH 1/2] Some typos --- service_container/3.3-di-changes.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/service_container/3.3-di-changes.rst b/service_container/3.3-di-changes.rst index c9c9580cc54..0b4d2cea615 100644 --- a/service_container/3.3-di-changes.rst +++ b/service_container/3.3-di-changes.rst @@ -360,7 +360,7 @@ The third big change is that, in a new Symfony 3.3 project, your controllers are But, you might not even notice this. First, your controllers *can* still extend the same base ``Controller`` class or a new :ref:`AbstractController `. This means you have access to all of the same shortcuts as before. Additionally, -the ``@Route`` annotation and ``_controller`` syntax (e.g.``AppBundle:Default:homepage``) +the ``@Route`` annotation and ``_controller`` syntax (e.g. ``AppBundle:Default:homepage``) used in routing will automatically use your controller as a service (as long as its service id matches its class name, which it *does* in this case). See :doc:`/controller/service` for more details. You can even create :ref:`invokable controllers ` @@ -433,7 +433,7 @@ In this case, you've created a class that implements ``EventSubscriberInterface` and registered it as a service. This is more than enough for the container to know that you want this to be used as an event subscriber: more configuration is not needed. And the tags system is its own, Symfony-specific mechanism. And of course, you can -always default ``autoconfigure`` to false in ``services.yml``, or disable it for a specific +always set ``autoconfigure`` to ``false`` (=default) in ``services.yml``, or disable it for a specific service. Does this mean tags are dead? Does this work for all tags? @@ -449,7 +449,7 @@ see what it autoconfigures. Many autoconfigured tags have an optional priority. If you need to specify a priority (or any other optional tag attribute), no problem! Just :ref:`manually configure your service ` -and add the tag. Your tag will take precedent over the one added by auto-configuration. +and add the tag. Your tag will take precedence over the one added by auto-configuration. What about Performance ---------------------- From 5bc4c4eba1f36ea9232a2fef53e16ad0a66db08a Mon Sep 17 00:00:00 2001 From: Thomas Landauer Date: Wed, 26 Jul 2017 20:52:53 +0200 Subject: [PATCH 2/2] Update 3.3-di-changes.rst As suggested by https://github.com/symfony/symfony-docs/pull/8230#pullrequestreview-52460591 --- service_container/3.3-di-changes.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/service_container/3.3-di-changes.rst b/service_container/3.3-di-changes.rst index 0b4d2cea615..bdb9438076c 100644 --- a/service_container/3.3-di-changes.rst +++ b/service_container/3.3-di-changes.rst @@ -433,7 +433,7 @@ In this case, you've created a class that implements ``EventSubscriberInterface` and registered it as a service. This is more than enough for the container to know that you want this to be used as an event subscriber: more configuration is not needed. And the tags system is its own, Symfony-specific mechanism. And of course, you can -always set ``autoconfigure`` to ``false`` (=default) in ``services.yml``, or disable it for a specific +always set ``autoconfigure`` to ``false`` in ``services.yml``, or disable it for a specific service. Does this mean tags are dead? Does this work for all tags?