On Aug 24, 2007, at 2:56 AM, Dan Korostelev wrote:
Yeah, I also worked around the problem this way, but I don't like it. Looks like there's a bug in Routes. Thanks for information.
There's no bug in routes, this is exactly how it works, and how the docs indicate it works. From the docs (http://routes.groovie.org/ manual.html): "We saw earlier how the route name ties a set of defaults to a name. We can use this name with our Route functions and its as if we used that set of keyword args"
The route name does *not* mean that the route its at will actually be the path generated. It means that the default args you give for that route will be pulled in as if you had specified them in the url_for.
Cheers, Ben
smime.p7s
Description: S/MIME cryptographic signature
