Describe weak_vendors properly

greg0ire · greg0ire · commit edcdcf88b7cb · 2018-07-23T21:50:07.000+02:00
The behavior has changed since #25997
diff --git a/src/Symfony/Bridge/PhpUnit/DeprecationErrorHandler.php b/src/Symfony/Bridge/PhpUnit/DeprecationErrorHandler.php
@@ -29,7 +29,7 @@ class DeprecationErrorHandler
      *
      * The following reporting modes are supported:
      * - use "weak" to hide the deprecation report but keep a global count;
-     * - use "weak_vendors" to act as "weak" but only for vendors;
+     * - use "weak_vendors" to fail only on deprecations triggered by your own code;
      * - use "/some-regexp/" to stop the test suite whenever a deprecation
      *   message matches the given regular expression;
      * - use a number to define the upper bound of allowed deprecations,

Original file line number	Diff line number	Diff line change
`@@ -29,7 +29,7 @@ class DeprecationErrorHandler`
`29`	`29`	`*`
`30`	`30`	`* The following reporting modes are supported:`
`31`	`31`	`* - use "weak" to hide the deprecation report but keep a global count;`
`32`		`- * - use "weak_vendors" to act as "weak" but only for vendors;`
	`32`	`+ * - use "weak_vendors" to fail only on deprecations triggered by your own code;`
`33`	`33`	`* - use "/some-regexp/" to stop the test suite whenever a deprecation`
`34`	`34`	`* message matches the given regular expression;`
`35`	`35`	`* - use a number to define the upper bound of allowed deprecations,`