Absolutely agree with you. On 23.02.2010, at 11:11, Prem Sichanugrist wrote:
> I'm oppose to this though. In my point of view, I think the name `match` is > already appropriate for it, as it mean that the router will try 'match' the > incoming request with each route, and sent the one that 'matched' to the > appropriate controller. On Feb 20, 2:13 pm, Jeff wrote: >> 1. It maintains continuity with previous versions of rails You MUST rewrite your routes anyway, so what a problem? Is it too hard to learn just 1 word? >> It's more descriptive of the intention of a route: to connect a >> requested url with an endpoint that can generate a response. As opposite, there are rules that must be "matched". -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
