the AttributeDriver will report fields for the classes where they are declared. This may uncover invalid mapping configurations.

[dimadeush]

Hello

First of all - Thanks for the great bundle!

It seems we have an issue and deprecation notice while using it and we hope that in the future issue will be fixed:

315x: In ORM 3.0, the AttributeDriver will report fields for the classes where they are declared. This may uncover invalid mapping configurations. To opt into the new mode today, set the "reportFieldsWhereDeclared" constructor parameter to true. (AttributeDriver.php:77 called by App_KernelTestContainer.php:587, https://github.com/doctrine/orm/pull/10455, package doctrine/orm

App_KernelTestContainer.php:587:
$a->addDriver(new \Doctrine\ORM\Mapping\Driver\AttributeDriver([(\dirname(__DIR__, 4).'/vendor/dukecity/command-scheduler-bundle/Entity')]), 'Dukecity\\CommandSchedulerBundle\\Entity');

With hope
Thanks in advance

[Chris53897]

I did add the config to the local test.
https://github.com/Dukecity/CommandSchedulerBundle/pull/146/files

I am not sure to change it here https://github.com/Dukecity/CommandSchedulerBundle/blob/main/DukecityCommandSchedulerBundle.php#L26

ORM 3.4

/**
     * @param array<string> $paths
     * @param true          $reportFieldsWhereDeclared no-op, to be removed in 4.0
     */
    public function __construct(array $paths, bool $reportFieldsWhereDeclared = true)
    {
        if (! $reportFieldsWhereDeclared) {
            throw new InvalidArgumentException(sprintf(
                'The $reportFieldsWhereDeclared argument is no longer supported, make sure to omit it when calling %s.',
                __METHOD__,
            ));
        }

        $this->reader = new AttributeReader();
        $this->addPaths($paths);
    }

[dimadeush]

Hello

Thanks for the response. Maybe we need to add there too, as it was done inside "doctrine/doctrine-bundle" here - https://github.com/doctrine/DoctrineBundle/blob/2.15.x/src/DependencyInjection/Compiler/DoctrineOrmMappingsPass.php#L160

Otherwise we will have deprecation notice for the doctrine 2.X versions. For the 3.X it's ok and we don't have deprecation notice as since 3.X the default value is true. Maybe since 4.X we can delete it.

WDYT?

Thanks in Advance