phpstan | PHP Static Analysis in Github Actions | Code Analyzer library

Your return annotation is wrong, as PhpStan is correctly reporting.

You say you report an array of roles:

I wanted to ignore the annotations from api doc, but it wasn't possible. Instead I can ignore the annotations from doctrine

I opened an issue on the github of phpstan-doctrine and i had an answer by @jlherren that explained :

The problem is that Doctrine needs to know what version of the DB server it is working with in order to instantiate the correct AbstractPlatform implementation, of which there are several available for the same DB vendor (e.g. PostgreSQL94Platform or PostgreSQL100Platform for postgres, and similarly for other DB drivers). To auto-detect this information, it will simply connect to the DB and query the version.

I just changed my database url from:

You need to configure objectManagerLoader so that the extension can see the entity metadata. This will allow DQL validation, and the correct entity repositoryClass to be inferred when accessing $entityManager->getRepository(). Add to your phpstan.neon:

PHPStan isn't going to run your code or look at your arguments to understand that this method is going to return a specific type of object -- it's just going to look at the method's return signature. Thus, from PHPStan's point of view, it's not guaranteed that getRepository() will return an instance of SpecificRepository, which means that it's not guaranteed that $this->repository will contain an instance of SpecificRepository. However, you've attempted to tell PHPStan just that via your @var typehint -- and PHPStan is (correctly) telling you that you're mistaken. To get the benefit of IDE autocompletion on a more specific class, you could typehint the attribute to its generic interface and then write a getter class that verifies the more specific class you're expecting:

I'm not sure if this is a bad practice, but it turned out I only had to remove that check from phpstan configuration.

Can you try the following:

Add this to your composer.json

Your format is incorrect, so Carbon cannot create the time. You're missing the T, which needs to be escaped.

Each recipe for a rule is a set of one or more shell commands (POSIX sh). So, the syntax you use to write recipes is the same as you'd use to write a shell script (or write shell commands at your shell prompt).

Also each logical line of the recipe is run in a different shell. So if you want to write your loop across multiple physical lines you need to add backslashes at the end to turn them into a single logical line. This may also mean you need semicolons so that the shell will understand what you want (this is all related to writing shell scripts, not makefiles). And, any time you want a $ to appear in your shell script you have to write it as $$ in your makefile, to escape the $ from make.

So one example: