minor #26251 Document the container.autowiring.strict_mode option (B-Galati)
This PR was merged into the 3.4 branch.
Discussion
----------
Document the container.autowiring.strict_mode option
| Q | A
| ------------- | ---
| Branch? | 3.4
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | https://github.com/symfony/symfony-docs/issues/8561
| License | MIT
| Doc PR | no
Hello,
Let me know for any misunderstanding from my part or rewording
Commits
-------
11383773bf
Document the container.autowiring.strict_mode option
This commit is contained in:
commit
4183e93825
@ -163,7 +163,18 @@ DependencyInjection
|
|||||||
autowire: true
|
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.
|
* `_defaults` and `_instanceof` are now reserved service names in Yaml configurations. Please rename any services with that names.
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user