Skip to content

Document the container.autowiring.strict_mode option #26251

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 1 commit into from
Feb 22, 2018
Merged

Document the container.autowiring.strict_mode option #26251

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 12 additions & 1 deletion UPGRADE-4.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,18 @@ DependencyInjection
autowire: true
```

* Autowiring services based on the types they implement is not supported anymore. Rename (or alias) your services to their FQCN id to make them autowirable.
* Autowiring services based on the types they implement is not supported anymore.
It will only look for an alias or a service id that matches a given FQCN.
Rename (or alias) your services to their FQCN id to make them autowirable.
In 3.4, you can activate this behavior instead of having deprecation messages
by setting the following parameter:

```yml
parameters:
container.autowiring.strict_mode: true
```

From 4.0, you can remove it as it's the default behavior and the parameter is not handled anymore.

* `_defaults` and `_instanceof` are now reserved service names in Yaml configurations. Please rename any services with that names.

Expand Down