It is by design - application programmers should be able to override routes previously defined by 3rd party bundles, for example.
t On Sat, Dec 10, 2011 at 03:31, Sebastian Hörl < hoerl.sebast...@googlemail.com> wrote: > Hi! > > When you define two routes with the same names in Symfony the first one > gets overridden by the second one. Because this can lead to confusion if > you define the routes in different controllers or bundles I wrote a small > patch that throws an exception if you try to define a duplicate > route. However I looked into the tests and noticed that there is a bunch of > test cases which exactly make sure that the routes are getting overridden > correctly. > So my question is: should everything stay as it is or should I modify the > tests and contribute the changes? > > Sebastian > > -- > 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 symfony-devs@googlegroups.com > To unsubscribe from this group, send email to > symfony-devs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- 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 symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
