-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[PhpUnitBridge] clarify silencing deprecations in tests #7323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
components/phpunit_bridge.rst
Outdated
* Make its data provider start with ``provideLegacy*()`` or ``getLegacy*()``. | ||
.. note:: | ||
|
||
You can make your data provider start with ``provideLegacy*()`` or ``getLegacy*()`` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to have more information about this:
- If I name a data provider as
provideLegacy()
andgetLegacy()
... will the tests that use that provider be considered legacy automatically? - If I declare a test as legacy ... am I required to call its data provider as
provideLegacy()
andgetLegacy()
too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, any comment about my questions? Thanks!
@javiereguiluz Sorry for the delay. I pushed an update here. Do you think it's more clear now? |
code, it is not required to choose a special naming just because the | ||
test being fed by the data provider is marked as legacy. | ||
|
||
Also be aware that choosing one of the two legacy prefixes will not mark |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"one of the" => "one of these"?
Thank you Christian. |
This resolves #7312.