This is a little known behavior of named routes that we didn''t
particularly like, but aceepted.
The rewritten routes that are in trunk resolve this.
- Original message -
(Appologies if this turns out to be a double post -- f...
On 7/21/06, Bosko Milekic <bosko.milekic@gmail.com>
wrote:> (Appologies if this turns out to be a double post -- from what
I''ve
> seen my first post seems to have gotten lost in the moderator''s
bin)
>
> Hi,
>
> I''m using Rails 1.1.4, so I appologize if edge has new routing
code
> and does not exhibit the behavior I describe here (in fact, could
> someone confirm if it does?)
>
> There seems to be a problem with named routes, one I think was not
> intentional. To the point, the generated name_url() code generates a
> URL to the highest-priority named route with the same combination of
> symbol keys in its path declaration. An example:
>
> map.first_route "first_route/:controller/:action/:id"
> map.second_route "second_route/:controller/:action/:id"
>
> Both first_route_url() and second_route_url() with
> :controller/:action/:id passed-in, generate
> "http://.../first_route/:controller/:action/:id".
>
> Routing authors, was this intentional or a side-effect of implementation?
>
> --
> Bosko Milekic <bosko.milekic@gmail.com>
> _______________________________________________
> Rails-core mailing list
> Rails-core@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails-core
>