di:setup:compile fails with anonymous classes

[joni-jones]

Preconditions (*)

The current implementation of \Magento\Setup\Module\Di\Code\Scanner\PhpScanner does not support classes that contain anonymous classes. This leads to failures for di:setup:compile command. The problem that PhpScanner treats anonymous classes as classes that might require code generation for factories and extension attributes.

All Magento versions have this issue.

Steps to reproduce (*)

1. Create a dummy class which contains an anonymous class, like Magento\DummyModule\Dummy (see a sample below)
2. Run bin/magento setup:di:compile CLI command

Expected result (*)

1. Compilation is successful

Actual result (*)

1. Compilation fails with an error Class \Magento\DummyModule\$arg does not exist

Sample class:

namespace Magento\DummyModule;

class Dummy
{
    public function execute($arg)
    {
        return new class($arg) {
            private $arg;

            public function __construct($arg)
            {
                $this->arg = $arg;
            }

            public function serialize()
            {
                return (string) $this->arg;
            }
        };
    }
}

To achieve the same error as described in #21555, the anonymous class should not provide a possibility to specify arguments for a constructor. In simple words, return new class {.

[m2-assistant]

Hi @joni-jones. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@joni-jones do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @joni-jones. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[slavvka]

Hi @joni-jones. Thank you for your report.
The issue has been fixed in #26533 by @joni-jones in 2.4-develop branch
Related commit(s):

• fd3f2a22b8e5b2cffaf17daccc29f461c26c5f51
• 136d5592244d05509ad0b3b9117505d8f833ddfa
• 25fd9259e72bc484f5899aa4edf3de120b66db0c
• e165d99f5994af39d49ed70155c003745158e5db

The fix will be available with the upcoming 2.4.0 release.