Skip to content

Update autowiring.rst #10625

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 5 commits into from
Nov 8, 2018
Merged

Update autowiring.rst #10625

Changes from 2 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
7b85a18
Update autowiring.rst
DonCallisto Oct 31, 2018
6ea7f5e
Update autowiring.rst
DonCallisto Oct 31, 2018
f325679
Update service_container/autowiring.rst
jmsche Nov 7, 2018
88faadd
Update service_container/autowiring.rst
jmsche Nov 7, 2018
42d8fb1
review fix
DonCallisto Nov 8, 2018
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
9 changes: 9 additions & 0 deletions service_container/autowiring.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -341,6 +341,15 @@ Thanks to the ``App\Util\TransformerInterface`` alias, the autowiring subsystem
knows that the ``App\Util\Rot13Transformer`` service should be injected when
dealing with the ``TransformerInterface``.

.. tip::

As long as you have only one concrete implementation of an interface under same
namespace, alias is not mandatory and autowire will work injecting the concrete
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would reword this a bit:

As long as there is only one class implementing the interface and that class is part of the same namespace configuring the alias is not mandatory and Symfony will automatically create one.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I'm gonna change to suggested sentence.

implementation even without alias definition.
Neverthless is recommended to provide an alias in order to preserve application
logic when a second concrete implementation kicks in, otherwise compiler compilation
would throw an exception.

Dealing with Multiple Implementations of the Same Type
------------------------------------------------------

Expand Down