Replace custom autoloaders with Magento's implementation

[shochdoerfer]

To investigate: Could we use the Magento\Framework\TestFramework\Unit\Autoloader implementations to generate the code and autoload it instead of our own custom logic? Or maybe reimplement Magento\Framework\Code\Generator\Autoloader to get rid of the ObjectManager magic.

[makao]

For Magento projects you can use

parameters:
    bootstrapFiles:
        - dev/tests/static/framework/Magento/PhpStan/autoload.php

Reference - Magento
Reference - PHPStan

For developing custom modules you need to create (copy) autoloader in your module to be able to run PHPStan without installing whole Magento.

[shochdoerfer]

Thanks for pointing out. That does make sense of course.

I am still undecided about how to drive this project forward as this project depends on a newer version of PHPStan compared to what Magento 2.4.0 depends on as outlined in #42.

[makao]

I think you shouldn't care which PHPStan version Magento is using as probably you don't want to test vendor code with it. I've used your package for testing project code located in app/code, we had used higher level than Magento is using and we were even patching some Magento core code to fix incorrect annotations.

When you create Magento project you can simply update your dev dependencies. Also every 3rd party module should test code itself, to sum up I think you should go with latest PHPStan, not latest used by Magento.

[shochdoerfer]

I just realized that we actually can't rely on Magento's autoloader for module projects because the autoloader is not shipped in one of Magento's Composer dependencies. Guess we'll have to keep our own solution for now.