The overall difference in configuration is pretty minimal. i.e.
adding:

routes-register="true" routes-prefix="_profiler"

As opposed to importing the routes manually:

<import resource="MyBundle/Resources/config/routing.xml" />

The manual importing ensures all routing is in the same place though
and is standardised.

-1 for me


On Jan 20, 4:11 am, Victor Berchet <[email protected]> wrote:
> Thanks for your feedback.
>
> I have update my branch with a third 
> commithttps://github.com/vicb/symfony/compare/vicb:master...vicb:router
>
> This commit implements what I suggested at the end of my last email:
> - making the automatic route reigstration optional,
> - adding the ability to cutomize the prefix.
>
> You can specify the options if your config file. i.e.
>     <webprofiler:config
>         toolbar="true"
>         intercept-redirects="true"
>         routes-register="true"
>         routes-prefix="_profiler"
>     />
>
> This should solve some the concerns (you can easily import an other
> resource if you don't like the default one).
>
> However I am still not convinced this (automatic registration) is a
> very good idea... .
>
> Victor.
>
> On Jan 18, 11:49 pm, Christophe COEVOET <[email protected]> wrote:
>
>
>
>
>
>
>
> > Le 18/01/2011 23:44, Bulat Shakirzyanov a crit :> I agree with Lukas here,
> > > You wouldn't want some extension to decide how the routes will look
> > > like, and maybe even hijack your own routes, depending on the order of
> > > extensions.
> > > This should be explicitly enabled by the end user.
>
> > Thus you can choose to overwrite the routes of a bundle if you don't
> > like the way the urls look by default. Currently you just add to define
> > the routes in your config and not import the bundle's file. It would be
> > far more difficult if they are automatically registered.
> > So -1 too
>
> > --
> > Christophe | Stof

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

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

Reply via email to