minor #26251 Document the container.autowiring.strict_mode option (B-Galati)

fabpot · fabpot · commit 4183e938254c · 2018-02-22T07:17:18.000+01:00
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 | symfony/symfony-docs#8561 | License | MIT | Doc PR | no Hello, Let me know for any misunderstanding from my part or rewording Commits ------- 1138377 Document the container.autowiring.strict_mode option
diff --git a/UPGRADE-4.0.md b/UPGRADE-4.0.md
@@ -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.
 
