On Thu, Nov 18, 2010 at 12:27 PM, Chris McDonough <chr...@plope.com> wrote:
> We need it to be able to match even when there is not necessarily a
> slash at the end of the URL pattern before the stararg starts (IOW, we
> need *fizzle to potentially become () if the path is /foo/baz/bar for
> the pattern "foo/:baz/:buz*fizzle"). This is how it's implemented and
> we count on this for *traverse behavior.
So...
/foo/b/c/la/la => buz="c", fizzle=("la", "la")
/foo/b/c => buz="c", fizzle=()
/foo/b/c/ => buz="c", fizzle=()
fooa/b/cd => buz="cd", fizzle=()
?
Routes considered the short URL (#2) an instance of minimization,
which led to ambiguities if it accidentally matched an unrelated URL
the programmer didn't intend. So the current Routes requires two
routes for this:
"/foo/:baz/:buz" , fizzle=""
"/foo/{baz}/{buz}/{fizzle:.*}"
These would both go to the same action.
Anyway, there may be problems with unintended minimization, especially
with a general route like:
/:action*fizzle
Or:
/section1/:action*fizzle
So I request "/help/faq" or "/help". Oh darn it, I meant that to go
to my "/help" or "/help/:section" route, not the "/:action{fizzle}"
route.
--
Mike Orr <sluggos...@gmail.com>
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-de...@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/pylons-devel?hl=en.
