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

Appearance settings

Commit d19266a

Browse filesBrowse files
committed
Merge branch '2.8' into 3.4
* 2.8: PhpUnitBridge: Fix typo in note
2 parents b10ea35 + a327949 commit d19266a
Copy full SHA for d19266a

File tree

1 file changed

+1
-1
lines changed
Filter options

1 file changed

+1
-1
lines changed

‎components/phpunit_bridge.rst

Copy file name to clipboardExpand all lines: components/phpunit_bridge.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -152,7 +152,7 @@ There are three ways to mark a test as legacy:
152152
.. note::
153153

154154
If your data provider calls code that would usually trigger a deprecation,
155-
you can prefix its name with ``provideLegacy`` or ``getLegacy`` to silent
155+
you can prefix its name with ``provideLegacy`` or ``getLegacy`` to silence
156156
these deprecations. If your data provider does not execute deprecated
157157
code, it is not required to choose a special naming just because the
158158
test being fed by the data provider is marked as legacy.

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.