On Feb 23, 12:36 am, Alexander Uvarov <[email protected]> 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?
I said criticism is ok, not personal attacks. Of course it's not too hard to learn. My point is that it's a change from every previous version of Rails that seems unnecesary to me. If it is not necessary, then it should not be done. > >> 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". That's been true since Rails 0.x. I think "connect" has been the right choice ever since, and I'm not seeing why we need to rename it to match(). My hope is that either someone on the core team will agree that it should remain as connect, or that someone from the core team will explain why a change is necessary. I'll be happy if either of those happen, because I will have learned something. Jeff -- 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.
