I'm currently updating a Rails Application from 3.1 to 3.2.
While trying to fix a failing test I noticed, that when you try to
generate an Url for a non existant Controller, this will not raise a
RoutingError, but generate an assets Url.

I also tried it in the rails console of a fresh generated app (3.2.1):

1.9.3p0 :001 > app.url_for :controller => 'foo'
=> "http://www.example.com/assets?controller=foo"
1.9.3p0 :002 >

The Problem is, that there are some functional tests in our
application which rely on pre 3.1 behaviour of raising RoutingErrors
when no route matches the provided params.

In my opinion, trying to generate a url where the params doesn't match
any route should clearly raise an exception.

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.

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouprubyonrails-talk @
postedFeb 16, '12 at 10:12a
activeFeb 16, '12 at 10:12a

1 user in discussion

Tea_moe: 1 post



site design / logo © 2023 Grokbase