On 23 Mrz., 18:33, Jonathan Wage <[email protected]> wrote: > It was a change made to fix a bug where if you generate a second admin > generator for the same Model but under a different module name, that the > route is unique. Thinking about it now we could have made it better so the > route is only modified if the existing route name already exists? Thoughts?
I would not "automagically" change the route name. I suggest to simply abort the task if the route already exists and add another option to allow changing the route name. Maybe even add a way to optionally overwrite an existing route - but this is tricky.. regards, Matthias > On Mon, Mar 23, 2009 at 8:30 AM, Matthias N. < > > > > [email protected]> wrote: > > > Hi, > > > following the Jobeet tutorial day 12 you can change the module of a > > generated admin generator module by the --module option. > > > But in this changeset: > > >http://trac.symfony-project.org/changeset/14983/branches/1.2/lib/plug... > > > The name of the generated route is changed so that the name of the > > generated module is appended and you get routes like: > > > jobeet_job_job > > jobeet_category_category > > > Why is that? I mean the --module option should only change the module > > name -- not the route name, shouln't it? > > > regards, > > Matthias > > -- > Jonathan H. Wage > Open Source Software Developer & > Evangelisthttp://www.jwage.comhttp://www.doctrine-project.orghttp://www.symfony-project.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
