-
-
Notifications
You must be signed in to change notification settings - Fork 708
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
Rector\CodingStyle\Rector\ClassMethod\ReturnArrayClassMethodToYieldRector should only apply to methods defined in a @dataProvider
annotation.
#2187
Comments
@dataProvider
annotation.@dataProvider
annotation.
Broken test would be great 👍 |
I've had a look at the existing fixtures (as I would have thought this issue would have been caught in there already), and I have to say that they are very obscure to me. I don't really understand what test cases they cover and how/why they are structured the way they are. |
What file exactly do we talk about? |
No need to explore old test cases, as they all passes. |
There you go : #2273 |
…tor/add-test-case-issue-2187 Add a working and a failing test case for #2187
rectorphp/rector-src@b055a88 Add RectorConfigProvider to ask for configuration behave for 3rd party packages (#2187)
I've added
config/set/phpunit/phpunit-yield-data-provider.yaml
to myimports
, which does the following :I would have assumed that this would apply only on methods targeted by a dataProvider, but it's not. I had a
private function getSomeData(): array;
method in a test that got changed by the Rector (furthermore, data providers in PHPUnit are alwayspublic
!).Is there something I misunderstood about the intended behavior of this config file ? Or should I try to add a broken test ?
The text was updated successfully, but these errors were encountered: