Routing in Rails 3 - Athens Ruby Meetup #4

RAILS 3Where

Routing gets awesome

Athens Ruby Meetup #4Nov. 11 2010

Thursday, November 11, 2010

Me

Σάββας ΓεωργίουSoftware engineer - Ruby on Rails Developer

http://healthleap.com




Routing in RailsEach time a request comes to the server, Rails needs to direct it to some action in some controller





"controller"=>"searches""action"=>"show", "id"=>"allergists",




Generates Paths and URLs




Generates Paths and URLs - photos_path returns /photos




Generates Paths and URLs - photos_path returns /photos- new_photo_path returns /photos/new




Generates Paths and URLs - photos_path returns /photos- new_photo_path returns /photos/new- photo_path(id) returns /photos/:id




Generates Paths and URLs - photos_path returns /photos- new_photo_path returns /photos/new- photo_path(id) returns /photos/:id- new_photo_url returns http://mydomain:port/photos/new


http://mydomain

http://mydomain



Generates Paths and URLs - photos_path returns /photos- new_photo_path returns /photos/new- photo_path(id) returns /photos/:id- new_photo_url returns http://mydomain:port/photos/new- new_photo_url(id) returns http://mydomain:port/photos/:id


http://mydomain

http://mydomain

http://mydomain

http://mydomain

Resources Routing


Resources Routingresources :photos





HTTP supports 4 verbs. GET, POST, PUT, DELETE

Browsers are dump enough to forget that, but rails can still make it with hidden parameters.


Resources Routing #2


Resources Routing #2new_photo_path()

GET for new

edit_photo_path()

GET for edit

photos_path()

GET for index

POST for create

photo_path(@photo)

GET for show

PUT for update

DELETE for destroy


Resources Routing #2new_photo_path()

GET for new

edit_photo_path()

GET for edit

photos_path()

GET for index

POST for create

photo_path(@photo)

GET for show

PUT for update

DELETE for destroy

We build internet applications over HTTP. We ‘d better use 100% of our protocol.


More Resources Routing - Members



What if we need more RESTful actions for our model?




resources :photos do member do get ‘preview’ get ‘print’ put ‘flag’ endend





preview_photo_path(@photo)print_photo_path(@photo)flag_photo_path(@photo)preview_photo_url(@photo)

.....

Available helpers





preview_photo_path(@photo)print_photo_path(@photo)flag_photo_path(@photo)preview_photo_url(@photo)

.....

Available helpers

GET /photos/:id/preview {:controller=>"photos", :action=>"preview"}GET /photos/:id/print {:controller=>"photos", :action=>"print"}PUT /photos/:id/flag {:controller=>"photos", :action=>"flag"}

Our Application responds to


More Resources Routing - Collections



resources :photos do collection do get ‘search’ endend




search_photos_pathsearch_photos_url

available helpers




search_photos_pathsearch_photos_url

available helpers

GET /photos/search {:controller=>"photos", :action=>"search"}



Named routes - Match


Named routes - MatchFor special cases and pretty URLs


Named routes - MatchFor special cases and pretty URLs

match ‘login‘ => ‘user_sessions#new’match ‘logout‘ => ‘user_sessions#destroy’

I.E. Login action looks better in /login than /user_sessions/new



GET /login {:controller=>"user_sessions", :action=>"new"}GET /logout {:controller=>"user_sessions", :action=>"destroy"}


For special cases and pretty URLs





GET /login {:controller=>"user_sessions", :action=>"new"}GET /logout {:controller=>"user_sessions", :action=>"destroy"}


For special cases and pretty URLs



login_path, login_url, logout_path, logout_url

Available Helpers


Routes Priority - the 1st WINS


Routes Priority - the 1st WINS- Routes are matches matched in top to bottom order as

they appear in the routes file




- The first route to match an incoming request wins





- Lower routes may never fire, if a higher route hides them by matching requests






>> rake routes






>> rake routes


Rails 3 vs Rails 2.3


Rails 3 vs Rails 2.3


Rails 3 vs Rails 2.3The old style map commands still work as before with a backwards compatibility layer, however this will be removed in the 3.1 release.


Rails 3 vs Rails 2.3The old style map commands still work as before with a backwards compatibility layer, however this will be removed in the 3.1 release.

The routes are attached to your application, which is now its own object and used throughout Railties






Rack it UP


Rack it UPIn Rails 3 we can have routes directly to Rack Applications.


Rack it UPIn Rails 3 we can have routes directly to Rack Applications.MyApplication::Application.routes do match "/home", :to => OtherAppend



-- (NOT) --



-- (NOT) --

In Rails 3 we can have routes ONLY to Rack Applications.



-- (NOT) --


match "/home", :to => “home#show”



-- (NOT) --



match "/home", :to => HomesController.action(:show)



-- (NOT) --



match "/home", :to => HomesController.action(:show)

HomesController.action(:show) returns a fully valid Rack application pointing at the show action of HomesController.


Better Constraints


Better ConstraintsNative support for subdomains





Regular Expressions in constraints







Constraints can be objects & can be specified in block form




Constraints can be objects & can be specified in block form



Thank you!

http://yehudakatz.com/2009/12/26/the-rails-3-router-rack-it-up/

http://guides.rubyonrails.org/routing.html

http://www.slideshare.net/GreggPollack/rails-3-beautiful-code-3219240

Resources














Technology

Routing in Rails 3 - Athens Ruby Meetup #4