mondrake

Another significant example: in PHPUnit, you may setup properties to be shared across multiple test cases, and will do so in the `TestCase::setUp()` method.

Ah yeah, Drupal has not installed phpstan-phpunit yet, https://www.drupal.org/project/drupal/issues/3326239

Thanks @weberhofer @lsolesen for your replies. Rather that transferring ownership, maybe we could just fork this repo somewhere else and you could mark this abandoned. It's not just the pel...

Anyone watching this: there is now a fork of this package at [FileEye/pel](https://github.com/FileEye/pel). Release 0.9.20 out there is PHP 8.2 and 8.3 compatible. The package is available on Packagist as...

Thanks @lsolesen, I will mark the pel/pel repository archived, and add a message to redirect to FileEye/pel.

Thanks for reviewing @stof. Did that, and changed the way the string is built if any text is passed with the annotation. Thought projects may have different requirements as to...

If it helps, we might change the annotation to be `@return-type-will-be-added` which is in fact what this PR is doing, and avoid confusion with the PHP native attribute.

@nicolas-grekas @stof @catch56 just a couple of points since this is originally coming from findings in Drupal. Regardless of the interpretations, the current state falls short for Drupal for two...

In Drupal we would not need that. If I understand correctly, we would have to find all the possible instances that will change BEFORE we do the change. What we...

Given that this seems controversial, I started working on a different approach, based on a PHPStan rule. That way we would also be able to baseline the errors.