Abder-Rahman Ali wrote: > In the "Head First Rails" book, it mentions this ordering in routes.rb: > > ActionController: : Routing: : Routes. draw do | map| > map. connect ' /ads/new' , : controller=>' ads' , : action=>' new' > map. connect ' /ads/create' , : controller=>' ads' , : action=>' > create' > map. connect ' /ads/' , : controller=>' ads' , : action=>' index' > map. connect ' /ads/: id' , : controller=>' ads' , : action=>' show' > > If we enter: > > map. connect ' /ads/: id' , : controller=>' ads' , : action=>' show' > > At the top of the ordering, how will that affect our routing. > > Can you just describe how to order routes in routes.rb? I mean, what is > the rule to follow when ordering routes? > > Thanks.
I'm not sure how old "Head First Rails" is, though I'm thinking 2008. If you're getting started take a look at Ruby on Rails Guides (as Colin mentioned), which has an excellent page for this topic: http://guides.rubyonrails.org/routing.html Using RESTful routes simplifies that that example is trying to achieve by a lot, and using them I rarely run into the precedence issue: map.resources :ads, :only => [:index, :new, :create, :show] -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en.
