Method "Symfony\Component\DependencyInjection\Extension\ExtensionInterface::load()" might add "void" as a native return type declaration in the future. Do the same in implementation "Hakam\MultiTenancyBundle\DependencyInjection\HakamMultiTenancyExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\DependencyInjection\Extension\PrependExtensionInterface::prepend()" might add "void" as a native return type declaration in the future. Do the same in implementation "Hakam\MultiTenancyBundle\DependencyInjection\HakamMultiTenancyExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\DependencyInjection\Extension\ExtensionInterface::load()" might add "void" as a native return type declaration in the future. Do the same in implementation "Pd\MenuBundle\DependencyInjection\PdMenuExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\DependencyInjection\Compiler\CompilerPassInterface::process()" might add "void" as a native return type declaration in the future. Do the same in implementation "Pd\MenuBundle\DependencyInjection\PdMenuExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\GenerateEntityFixturesCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
The "Symfony\Component\Console\Command\Command::$defaultName" property is considered final. You should not override it in "App\Command\GenerateEntityFixturesCommand".
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\FilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\FilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\FilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Since doctrine/doctrine-bundle 2.12: The default value of "doctrine.orm.controller_resolver.auto_mapping" will be changed from `true` to `false`. Explicitly configure `true` to keep existing behaviour.
Since doctrine/doctrine-bundle 2.13: Enabling the controller resolver automapping feature has been deprecated. Symfony Mapped Route Parameters should be used as replacement.
Return type of Pd\MenuBundle\Builder\Item::offsetExists($childId) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Return type of Pd\MenuBundle\Builder\Item::offsetGet($childId) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Return type of Pd\MenuBundle\Builder\Item::offsetSet($childId, $order) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Return type of Pd\MenuBundle\Builder\Item::offsetUnset($childId) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Method "ArrayAccess::offsetExists()" might add "bool" as a native return type declaration in the future. Do the same in implementation "Pd\MenuBundle\Builder\Item" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "ArrayAccess::offsetGet()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "Pd\MenuBundle\Builder\Item" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "ArrayAccess::offsetSet()" might add "void" as a native return type declaration in the future. Do the same in implementation "Pd\MenuBundle\Builder\Item" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "ArrayAccess::offsetUnset()" might add "void" as a native return type declaration in the future. Do the same in implementation "Pd\MenuBundle\Builder\Item" now to avoid errors or add an explicit @return annotation to suppress this message.
Since symfony/security-bundle 6.2: The "Symfony\Component\Security\Core\Security" service alias is deprecated, use "Symfony\Bundle\SecurityBundle\Security" instead. It is being referenced by the ".service_locator.YgYapZ6" service.
Since symfony/console 6.1: Relying on the static property "$defaultName" for setting a command name is deprecated. Add the "Symfony\Component\Console\Attribute\AsCommand" attribute to the "App\Command\GenerateEntityFixturesCommand" class instead.
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_KernelDevDebugContainer.php:1755, https://github.com/doctrine/orm/pull/10455, package doctrine/orm)
Not enabling lazy ghost objects is deprecated and will not be supported in Doctrine ORM 3.0. Ensure Doctrine\ORM\Configuration::setLazyGhostObjectEnabled(true) is called to enable them. (ProxyFactory.php:166 called by EntityManager.php:177, https://github.com/doctrine/orm/pull/10837/, package doctrine/orm)
JoinColumn configuration is not allowed on the inverse side of one-to-one associations, and will throw a MappingException in Doctrine ORM 3.0 (ClassMetadataInfo.php:1865 called by ClassMetadataInfo.php:2946, https://github.com/doctrine/orm/pull/10654, package doctrine/orm)
User Deprecated: 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_KernelDevDebugContainer.php:1755, https://github.com/doctrine/orm/pull/10455, package doctrine/orm)
User Deprecated: Not enabling lazy ghost objects is deprecated and will not be supported in Doctrine ORM 3.0. Ensure Doctrine\ORM\Configuration::setLazyGhostObjectEnabled(true) is called to enable them. (ProxyFactory.php:166 called by EntityManager.php:177, https://github.com/doctrine/orm/pull/10837/, package doctrine/orm)
"SELECT t0.id AS id_1, t0.name AS name_2, t0.base_price AS base_price_3, t0.logo AS logo_4, t0.description AS description_5, t0.type AS type_6, t0.created_at AS created_at_7, t0.updated_at AS updated_at_8, t0.deleted AS deleted_9, t0.deleted_at AS deleted_at_10 FROM plan t0"
doctrine
[
"sql" => "SELECT t0.id AS id_1, t0.name AS name_2, t0.base_price AS base_price_3, t0.logo AS logo_4, t0.description AS description_5, t0.type AS type_6, t0.created_at AS created_at_7, t0.updated_at AS updated_at_8, t0.deleted AS deleted_9, t0.deleted_at AS deleted_at_10 FROM plan t0"
]