That is what I have since done. It turns out that you can use ->get to fetch the in-URL parameters as well as query string parameters, so you can still write actions that don't care what the route looks like, which I think is an important feature.
So my third question is answered, but the first and second are still somewhat up in the air (: You can write two routes for everything to handle the empty-string case while still having pretty URLs, but this means you can't make a simple path() call and pass the variable without worrying about what it is anymore. -- 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 users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
