- Issue created by @mstrelan
- 🇮🇹Italy mondrake 🇮🇹
A nice alternative would be to add https://github.com/ergebnis/phpstan-rules as a dev dependency, enable the https://github.com/ergebnis/phpstan-rules?tab=readme-ov-file#functionsno... rule, add the failures of the current codebase to the baseline, and have PHPStan report all new code missing the statement.
- 🇦🇺Australia mstrelan
Yeah we could do that instead if we can tolerate an even larger baseline. We'd need a dependency evaluation, or we could write our own phpstan rule to skip the additional dependency.
- 🇺🇸United States dww
Slick, thanks for working on this!
IMHO, adding 28 lines to
.gitlab-ci.yml
seems vastly preferable to both a new dev dependency and an even larger PHPStan baseline. - 🇮🇹Italy mondrake 🇮🇹
Let's try #3 in a separate MR, and see what that brings. That extension provides at least another rule that we could leverage.
- 🇺🇸United States dww
Re #3/#6. The pipeline in the new MR failed with:
4384 ergebnis.declareStrictTypes
(among other things). Ugh. I know how much we love to "get off the island", but IMHO, the 28 line diff to.gitlab-ci.yml
is vastly superior for all sorts of reasons.