Conversation
mfn
left a comment
There was a problem hiding this comment.
Very nice!
Since there's no github action implemented for this repo and I'm unable to see if the test suite was properly executed with this Scrutinizer, I checked out the code locally and let the test suite run -> all green \o/
~/src/phpstan-strict-rules ⎇ phpstan_v2
$ vendor/bin/phpunit
PHPUnit 9.6.22 by Sebastian Bergmann and contributors.
...... 6 / 6 (100%)
Time: 00:00.737, Memory: 68.00 MB
OK (6 tests, 6 assertions)
Generating code coverage report in Clover XML format ... done [00:00.001]
Generating code coverage report in HTML format ... done [00:00.011]
Code Coverage Report Summary:
Classes: 100.00% (7/7)
Methods: 100.00% (14/14)
Lines: 100.00% (120/120)
|
@shish I've seen you active on other repos here, do you have any plans/interest/permission to also handle this repo? Or do you know who can? |
I've implemented a gha workflow on my fork to test if everything works. I can send that too (in a separate PR) |
I was only given access to |
|
Honest / friendly question: should we fork it? Those who are using it are locked from upgrading to Laravel 12. |
I needed this for my projects, I've forked it (https://packagist.org/packages/kcs/phpstan-strict-rules). |
I've updated the rules to be compatible with phpstan 2, dropping the support for phpstan 1.
Rules now returns an array of objects (instance of
RuleError) instead of strings.Hints are now added to
RuleErrorobject usingRuleErrorBuilder::tipmethod.Fix #66