Sinatra has a great way of defining routing. You define a route, and then define exactly how it responds right in that same spot. Just the right amount of magic! The routes have only a few basic forms, but it’s more than enough to handle most any situation. In my examples I use get, but there’s no reason you can’t use the same routing with post, put, or delete

No option route

get '/about' do
  haml :about
end

Single option

get '/thing/:id' do
  @thing = Thing.find(params[:id])
  haml :thing_show
end

Multiple options

get '/thing/:id/subthing/:subid' do
  @thing = Thing.find(params[:id])
  @subthing = SubThing.find(params[:subid])
  haml :subthing_show
end

Handling file formats

get '/thing.:format' do
  case params[:format]
  when 'xml'
    render_xml
  when 'json'
    render_json
  end
end

Handling full subfolders
This one is ugly. There’s apparently a feature request + possible patch out there (as mentioned on the mailing list, but it hasn’t been implemented yet.

get '/archive/*' do
    star_depth = 1 # /archive comes before the *
    splat = request.path_info.split('/')[(star_depth + 1)..-1].join('/')
    splat
end

This entry was posted on Saturday, May 17th, 2008 at 8:35 pm and is filed under Programming, Ruby, Sinatra. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.