Don't work Foo&PHPUnit_Framework_MockObject_MockObject

[marksartdev]

Don't work comments Foo&PHPUnit_Framework_MockObject_MockObject and Foo&MockObject

/**
* @return Foo&MockObject
*/
private function createSomeMock()
{
    $mock = $this
        ->getMockBuilder(Foo::class)
        ->setMethodsExcept(['foo', 'bar'])
        ->setConstructorArgs([])
        ->getMock();

    return $mock;
}

phpstan error: PHPDoc tag @return contains unresolvable type.

phpstan version: 0.12.37
phpstan-phpunit version: 0.12.16

[ondrejmirtes]

Do you have use PHPUnit\Framework\MockObject\MockObject above the class?
What version of PHPUnit do you have?

[marksartdev]

Do you have use PHPUnit\Framework\MockObject\MockObject above the class?
What version of PHPUnit do you have?

Yes.
7.5.20

[ondrejmirtes]

I have the same version and it works for me right in PHPStan sources themselves: https://github.com/phpstan/phpstan-src/blob/86a3b5699a7baa45247bf3fe8665d17b73dfb69e/tests/PHPStan/Parser/CachedParserTest.php#L87

Please create a small reproducing repository so I can debug the problem for you.

[marksartdev]

Ok. I'm preparing repository.

[marksartdev]

https://github.com/Mark-Sart/phpstan-phpunit-issue
In this repository I tried to repeat my issue. I installed some libraries in this repository like in my real project.

[ondrejmirtes]

Solved: https://github.com/Mark-Sart/phpstan-phpunit-issue/pull/1

[marksartdev]

I have some problems yet.
In general, it is work, but if I change my baseline I have error PHPDoc tag @return contains unresolvable type.
In my opinion, it happen when I have cash of target file and I change my base-line. But if I change target file or remove cache,
phpstan works correctly.

[ondrejmirtes]

Can you give me a set of steps to reproduce this on that repository?

[marksartdev]

On that repository phpstan work correct. Problem only on my productive repository. Maybe repo must be bigger.

[ondrejmirtes]

So reproduce it 🤷

[marksartdev]

I'll try to reproduce it on test repository.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.