Named route with :path_prefix opt, is generated incorrectly when called from a test
Reported by Vova Z | July 23rd, 2008 @ 01:37 AM | in 2.x
Here is an example: http://pastie.org/239105
It works if I open: http://localhost:3012/a/1/2/new. Also, it works if I pass all params into my_new_post_path(:a => 1, :b => 2, :foo => 3). It also works if I remove :path_prefix from a route definition, like this:
map.my_new_post "a/:a/:b/new", :controller => "posts", :action => "show"
Comments and changes to this ticket
-
Pratik July 23rd, 2008 @ 05:41 AM
- → State changed from “new” to “invalid”
-
Vova Z July 23rd, 2008 @ 03:11 PM
I'm sorry, but does this mean that I need to pass all params explicitly?
If I have:
map.a "a", :path_prefix => "path1/:param1/:param2", ...
And if I want my tests to work correctly, I can't use a_path() - without params, even if I already have all required params in URL. Instead, I should always use a_path(:param1 => params[:param1], :param2 => params[:param2])?
Then, what is the difference between:
map.a "a", :path_prefix => "path1/:param1/:param2", ...
and
map.a "path1/:param1/:param2/a", ...
Why first named route does not work (in ftests), and the last one is OK?
Thank you.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
git clone git://github.com/rails/rails.git
The latest development for the 1.2.x and 2.0.x releases are on the 1-2-stable and 2-0-stable branches.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".
