On Thu, Nov 18, 2010 at 11:20 PM, Fabien Potencier
<fabien.potenc...@symfony-project.com> wrote:
> But, :something has no special meaning in PHP and so, this is just a
> convention.
Another problem, iirc you can't do: /:foo:bar at the moment, and
/:foosomething where you just want :foo as a param name is also
impossible anyway.
> /article/{id}
This syntax with proper ending delimiters sounds more robust.
> It does not make sense to implement the whole specification in our context,
> and so I'm just proposing to use the same conventions described in the
> specification.
Some other stuff like the path ( {+path}/here => /foo/bar/here ) seem
quite useful as well.
Anyways I'm definitely +1 on this. This seems like a great step forward.
Something I would love to see though is the opportunity to have an
optional trailing slash at the end. At the moment this is very hard to
achieve nicely, and this is something that bothers me quite a lot
actually. /:id/? is what I'm after. Seems like the spec has some
things relating to that but it's not yet complete so it's hard to get
meaning out of all those examples.
Also being able to just specify default values in there could be nice,
but I think the ability to do it in the 'defaults' array should
remain, because sometimes you have pretty long stuff as default and
the pattern will get really ugly.
Cheers
--
Jordi Boggiano
@seldaek :: http://seld.be/
--
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
