Christophe Coevoet

Proper usage of the callable lifetime tags should be enforced in static analysis

1

### Feature request If `@param-immediately-invoked-callable` is applied on a parameter, storing the callable for later usage should report an error about this invalid usage. Similarly, if `@param-later-invoked-callable` is applied on...

phpstan messes up the type of constants containing array shapes when they have too many entries

10

### Bug report See https://github.com/scssphp/scssphp/pull/711/files#diff-13089a54481b0ddc2d096cc9a10d51a13270053cbd7acb896887b2d49e959fdf for the impacted file. Removing a few entries from the array in the `BUILTIN_FUNCTIONS` constant makes the analysis pass. I added a `@var` phpdoc on...

The playground reports false positives about changing the return type to never

3

### Bug report When a method is overridden in the code snippet, the playground should not suggest changing the return type of the parent method to `never` as this would...

Excluding all enum cases one by one does not simplify a return type when using `getAllowedSubTypes` involving an enum

6

### Bug report When an extension implements `getAllowedSubTypes` to define that the only allowed subtypes of an interface are a given class and an enum, I would except that handling...

Label translation parameters should not inherit from a form to its children

3

### Symfony version(s) affected 6.3 ### Description Currently, `\Symfony\Component\Form\Extension\Core\Type\BaseType::buildView` merges the `label_translation_parameters` and `attr_translation_parameters` from the parent with the one. This was unnoticed until now because the translation parameters defined...

Some RFCs are marked as accepted for an unspecified PHP version

1

See https://php-rfc-watch.beberlei.de/#Accepted%20RFCs%20for%20PHP%20

I'm talking about these texts:  Here are the contrast ratio: - white on green: 1.86 - white on red: 2.44 - white on blue: 2.28 - white on teal...

A yes-no vote always displays the `no` vote last, meaning you first have the choice for something changing and then the choice for doing nothing. And that's displayed this way...

you are adding use statements, but without checking if they could conflict with other classes in the same namespace (possible only if the user try to typehint a class `...\Base*`...

Currently, if an invalid name is used, the behavior simply skips it silently. This makes it very difficult to spot typos in the config of the behavior. The [filter function](https://github.com/willdurand/TypehintableBehavior/blob/master/src/TypehintableBehavior.php#L103)...