New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DDC-2031: doctrine:generate:entities - Alternate (scoped) Namespace Syntax not supported #2709
Comments
Comment created by @Ocramius: [~ilaurillard] entities are per-file anyway, you'd have only one namespace.
is exactly like writing
|
Comment created by ilaurillard: One namespace per file may be correct, but only considering autoloading issues. 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 created by @Ocramius: [~ilaurillard] not really sure classcache is doctrine's problem. Playing with reflection, any third party (Symfony2 here) can handle that without string concat |
Comment created by stof: @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 created by @Ocramius: [stof] 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 [ilaurillard] exposed as an example is anyway a bit weak. I don't see this coming without code generation projects going on first. |
Comment created by @Ocramius: Alternate code generators project is not yet on roadmap. |
Issue was closed with resolution "Won't Fix" |
Jira issue originally created by user ilaurillard:
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!
The text was updated successfully, but these errors were encountered: