Allows entities to be extended by a custom parent class

[Prometee]

This PR is allowing to extends the 2 Doctrine entities available.

• Swicth to XML mapping (not required but it will if this plugin wants to support PHP 8.1 one day).
• Make properties protected instead of private.
• Switch from Doctrine Table to MappedSuperClass to allow overrides.
• Add overrided entities to the flex recipe to test the override ?

Note: I saw some entity properties are nullable but they aren't when you look at the database schema definition.

[jacquesbh]

LGTM

[jacquesbh]

@Prometee The null properties are correct. We use them to avoid issues with Doctrine, since you can't access a property which hasn't been set in the first place. null becomes then the default value. But everything in the code disallows those values to be null elsewhere out of the PHP class.

[delyriand]

LGTM

And I think we will leave for later the last point of the TODO concerning the entity override test.

[Prometee]

@lanfisis or @delyriand Can you run one last time the build to see if everything is ok ?

[lanfisis]

@lanfisis or @delyriand Can you run one last time the build to see if everything is ok ?

Done, it's running

[maximehuran]

Thank you @Prometee the doctrine is not up to date, if I run a diff :

        $this->addSql('ALTER TABLE mbiz_alert_message CHANGE enabled enabled TINYINT(1) DEFAULT true NOT NULL, CHANGE customers_only customers_only TINYINT(1) DEFAULT false NOT NULL, CHANGE created_at created_at DATETIME NOT NULL, CHANGE template_html template_html VARCHAR(255) DEFAULT NULL');

It seems the default value is true instead of 1 and false instead of 0.

[Prometee]

@maximehuran that's what I saw to, I just fixed it 😉

[maximehuran]

It stills have

CHANGE created_at created_at DATETIME NOT NULL, CHANGE template_html template_html VARCHAR(255) DEFAULT NULL

[Prometee]

@maximehuran my bad I did not scroll right 😅
I fixed all types it should be good now, you can re-run the build now.

[maximehuran]

Thank you very much @Prometee 🫶