Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit6301a75

Browse files
committed
Document weak lagging vendors mode
Refssymfony/symfony#24867
1 parent75552f9 commit6301a75

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

‎components/phpunit_bridge.rst‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -171,6 +171,15 @@ the ``vendors`` directory will make the test suite fail, while deprecations
171171
triggered from a library inside it will not, giving you the best of both
172172
worlds.
173173

174+
When working on a project, you might be more interested in the
175+
``weak_lagging_vendors``, which is a bit more strict. Let's say you want to fix
176+
deprecations as soon as they appear. A problem many people experience is that
177+
some dependencies they have tend to lag behind their own dependencies, meaning
178+
they do not fix deprecations as soon as possible, which means there is nothing
179+
you can do to fix that (apart from a pull request on the lagging vendor). This
180+
mode allows you to ignore those deprecations, allowing you to notice when your
181+
code is using deprecated APIs, and to keep up with the changes.
182+
174183
Disabling the Deprecation Helper
175184
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
176185

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp