Skip to content

Update 3.3-di-changes.rst #9813

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.

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
May 27, 2018
Merged
Changes from all commits
Commits
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: 3 additions & 1 deletion service_container/3.3-di-changes.rst
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
The Symfony 3.3 DI Container Changes Explained (autowiring, _defaults, etc)
===========================================================================

If you look at the ``services.yml`` file in a new Symfony 3.3 project, you'll
If you look at the ``services.yml`` file in a new Symfony 3.3 or newer project, you'll
notice some big changes: ``_defaults``, ``autowiring``, ``autoconfigure`` and more.
These features are designed to *automate* configuration and make development faster,
without sacrificing predictability, which is very important! Another goal is to make
Expand Down Expand Up @@ -597,6 +597,8 @@ to the new id. Create a new ``legacy_aliases.yml`` file:

# app/config/legacy_aliases.yml
services:
_defaults:
public: true
# aliases so that the old service ids can still be accessed
# remove these if/when you are not fetching these directly
# from the container via $container->get()
Expand Down