[DCOM-73] CodeGeneration using Doctrine\Common\Persistence\Mapping\ObjectMetadata

Thu, 16 Feb 2012 19:27:38 +0000

Currently we have tons of code in the ODM/ORMs regarding code generation that are ugly to extend and maintain. We should extract all them into a new component, for example named: doctrine-code-generator

It should be feed by only instances of Doctrine\Common\Persistence\Mapping\ObjectMetadata into a twig template.
A base template for an entity/document is shipped
Maybe ORM/ODM specific child templates or twig traits are necessary to handle writing annotations. This could also be done by adding hooks into the code-generation somehow.
Each entity of the user can provide its own template, for examples from a configurable directory "code_templates/Vendor.ProjectBundle.Entity.User.twig" to extend the base template and add own code.
As a perspective we should aim for 5.4 generating a trait so that you can have your entity "class User { use UserBase; }
"

[DCOM-28] Extract Common Persistance Interfaces

Duplicate — Sat, 30 Jul 2011 13:03:50 +0000

I discussed this with jwage on symfony day cologne and this also came up during discussions with @dzuelke at IPC yesterday. So i hacked up a first patch for discussion that adds a Doctrine\Common\Persistance namespace and extracts the functionality all our 3 layers implement with regards to EntityManager/EntityRepository (and equivalents).

Additionally i think it might make sense to also add an interface "ObjectMetadata" that has several getters-only that allow access to the field, identifier and association mapping information. This stuff is not necessarly compatible across layers when returned as its "array" representation, but for libraries hooking into the metadata (symfony admin generator) this might not even be necessary.

Doctrine Project

[DCOM-73] CodeGeneration using Doctrine\Common\Persistence\Mapping\ObjectMetadata

[DCOM-28] Extract Common Persistance Interfaces