Skip to content

Some typos #8230

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

Closed
wants to merge 2 commits into from
Closed

Some typos #8230

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
78fcf0a
Some typos
ThomasLandauer Jul 26, 2017
5bc4c4e
Update 3.3-di-changes.rst
ThomasLandauer Jul 26, 2017
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
6 changes: 3 additions & 3 deletions service_container/3.3-di-changes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <controller-abstract-versus-controller>`.
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 <controller-service-invoke>`
Expand Down Expand Up @@ -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`` in ``services.yml``, or disable it for a specific
service.

Does this mean tags are dead? Does this work for all tags?
Expand All @@ -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 <services-manually-wire-args>`
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
----------------------
Expand Down