-
-
Notifications
You must be signed in to change notification settings - Fork 431
fix: SafeDeclareStrictTypesRector #7856
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
f23650b to
62502b8
Compare
62502b8 to
46664d7
Compare
|
@samsonasik, this should be good to go---after some digging I found that PHPStan is a very lenient with With these changes Rector safely updated ~1500 of my files and the pest and phpstan ci jobs passed |
46664d7 to
f629d5d
Compare
|
@samsonasik, done 👍 |
|
Thank you @calebdw |
|
@TomasVotruba @samsonasik, any chance it can be released soon? |
|
@MrPunyapal you can try dev-main for now, it now excluded from sets as require more tests on real life project, see: |
|
Thanks for update |
Just replicating the failure for now---this seems to be a phpstan bug, the following is returning true when it should be returning false:
This should be
Maybebecause the$valueTypemight not be aint|float, but instead phpstan is saying this isYes