Question

DocumentsController#common_query can handle multiple different request styles.

i.e. all docs in batch 4 or all docs tagged ‘happy’

I want a single route to make em pretty, so:

/documents/common_query?batch=4

/documents/common_query?tag=happy

become:

/documents/batch/4

/documents/tag/happy

So the end result is that #common_query is called but part of the url was used as the param name and part as it’s value.

Answer 1

As a single route:

ActionController::Routing::Routes.draw do |map|   map.connect 'documents/:type/:id', :controller => 'documents_controller',                :action => 'common_query' end 

Then params[:type] will either be 'batch' or 'tag', and params[:id] either '4' or 'happy'. You will have to make sure that other actions for the DocumentsController come before this in the routes because this will match any url that looks like 'documents/*/*'.

But why does it have to be a single route? You could use two routes like this:

map.with_options(:controller => 'documents_controller',                   :action => 'common_query') do |c|   c.connect 'documents/batch/:page', :type => 'batch'   c.connect 'documents/tag/:tag',    :type => 'tag' end 

which will have the same effect, but is more specific, so you wouldn’t have to worry about the priority order of the routes.