mirror of
https://github.com/doctrine/orm.git
synced 2026-03-24 06:52:09 +01:00
DDC-398: AnnotationExporter does not generate nice PHP classes #497
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @doctrinebot on GitHub (Mar 9, 2010).
Originally assigned to: @jwage on GitHub.
Jira issue originally created by user @guilhermeblanco:
We should update AnnotationExporter to generate nice PHP outputs, including doc blocks.
This would require the DBAL\Type to have a method called Type::getPhpTypeName(), to allow retrieval in docblocks.
@doctrinebot commented on GitHub (Mar 14, 2010):
Comment created by shurakai:
Please see my mail to the devlist, dated 2010/01/10, topic "[doctrine-dev] Doctrine2: Use CodeGenerator classes for generators?".
I think this is still preferable.
@doctrinebot commented on GitHub (Mar 20, 2010):
Comment created by @jwage:
I added \Doctrine\ORM\Tools\EntityGenerator which is an API for generating entity classes from ClassMetadataInfo instances. It is used in the AnnotationExporter and the GenerateEntitiesTask now. It isn't as generic as the Zend Code Generator component. Though if we wanted to we could make the EntityGenerator use that Zend Framework component to generate the code. It may be overkill though. Comments?
@doctrinebot commented on GitHub (Mar 20, 2010):
Comment created by romanb:
I think our current code-generation needs are simple enough that we can handle them ourselves without a new third-party dependency. Once/if it gets out of control, we can still make the switch.
@doctrinebot commented on GitHub (Mar 20, 2010):
Comment created by @beberlei:
I also worked with that CodeGenerator for Proxy Generation in Zend Entity and it has some problematic issues that are not addressed yet.
@doctrinebot commented on GitHub (Apr 23, 2010):
Issue was closed with resolution "Fixed"