[DDC-2031] doctrine:generate:entities - Alternate (scoped) Namespace Syntax not supported Created: 13/Sep/12  Updated: 23/Jan/13  Resolved: 23/Jan/13

Status: Closed
Project: Doctrine 2 - ORM
Component/s: None
Affects Version/s: None
Fix Version/s: None
Security Level: All

Type: Bug Priority: Minor
Reporter: Ilja Laurillard Assignee: Marco Pivetta
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

My preferred Syntax:

namespace foo
{
use ...;
class

{ ... }

}

seems not to be supported.

Setters/Getters are inserted before the last curly closing bracket - but that is the closing Namespace scope!



 Comments   
Comment by Marco Pivetta [ 13/Sep/12 ]

Ilja Laurillard entities are per-file anyway, you'd have only one namespace.

namespace Foo
{
    use AAA;
    class Bar {}
}

is exactly like writing

namespace Foo
use AAA;
class Bar {}
Comment by Ilja Laurillard [ 14/Sep/12 ]

One namespace per file may be correct, but only considering autoloading issues.
Have a look to the symfony "bootstrap.php.cache" file for an example of multiple namespace and classes.
Doctrine should have a similar "compiling" option.

I know of the standard syntax - thats why i wrote: "my preferred syntax".

I just may live with the standard syntax - you may want to at least mention in the docs that you have to use standard syntax, else your compiled entities fatal.

Comment by Marco Pivetta [ 14/Sep/12 ]

Ilja Laurillard not really sure classcache is doctrine's problem. Playing with reflection, any third party (Symfony2 here) can handle that without string concat

Comment by Christophe Coevoet [ 14/Sep/12 ]

@Marco The issue is not about creting a class cache but about editing entities with the EntityGenerator when the code uses the syntax with braces.

Comment by Marco Pivetta [ 14/Sep/12 ]

Christophe Coevoet yes, but I think the code generator becomes quite too complex when we add all these details... What I was thinking is that using an alternate syntax to ease the task Ilja Laurillard exposed as an example is anyway a bit weak. I don't see this coming without code generation projects going on first.

Comment by Marco Pivetta [ 23/Jan/13 ]

Alternate code generators project is not yet on roadmap.

Generated at Mon Oct 20 13:19:07 UTC 2014 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.