Markus Staab
Markus Staab
> The alternative is that you still include phpstan itself in the build-infection. on phpstan-src side, I already fixed it by upgrading the relevant lib in https://github.com/phpstan/phpstan-src/pull/4617
I wonder why infection needs the application-under-test autoloader at all...? To find custom mutators?
ohh nice, I didn't realize we have something similar already. my request was about ignoring a single mutator, so something like `@infection-ignore ` e.g. [in my recent PR](https://github.com/infection/infection/pull/2289/files) I would...
@ondrejmirtes to properly solve this we maybe should turn `ReflectionProvider->hasFunction` from `bool` to `TrinaryLogic` in 2.x?
we also see this issue
> do a first pass of the AST before generating any mutation. I plan to open dedicated epic/RFC for it, but I have a question that can already be debated...
I would go with one of the allowFloatBoolNullAsArrayKey variants, as otherwise we need to document somewhere what "loose" or "strict" means in this context
I am travelling atm. Can have a look in a few days
> There are deprecations thrown in `RuleSetTest::provideAllRulesFromSetsCases`, which in PHPUnit 12 [fails](https://github.com/sebastianbergmann/phpunit/pull/6293) the tests. > > Adding `PHPUnit\Framework\Attributes\IgnoreDeprecations` to those tests somehow started to fail other ones. could you be...
I think streaming the TestRunners output instead of building our tool agnostic on top has the following benefits - people get the output of their test tool of choice, which...