RSpec
Ruby on Rails
Ruby
method
generate
v4.0.2 -
Show latest stable
-
1 note -
Class: ActionDispatch::Routing::RouteSet::Generator
- 1.0.0
- 1.1.6
- 1.2.6
- 2.0.3
- 2.1.0
- 2.2.1
- 2.3.8
- 3.0.0 (0)
- 3.0.9 (0)
- 3.1.0 (0)
- 3.2.1 (0)
- 3.2.8 (0)
- 3.2.13 (0)
- 4.0.2 (38)
- 4.1.8 (0)
- 4.2.1
- 4.2.7
- 4.2.9
- 5.0.0.1
- 5.1.7
- 5.2.3
- 6.0.0
- 6.1.3.1
- 6.1.7.7
- 7.0.0
- 7.1.3.2
- What's this?
-
new
-
controller
-
current_controller
-
different_controller?
-
generate
-
handle_nil_action!
-
named_route_exists?
-
normalize_action!
(>= v4.1.8)
-
normalize_controller!
-
normalize_controller_action...
-
normalize_options!
-
normalize_recall!
(>= v4.1.8)
-
opts
(<= v3.0.9)
-
raise_routing_error
(<= v3.2.13)
-
segment_keys
-
use_recall_for
-
use_relative_controller!
= private
= protected
generate()
public
Generates a path from routes, returns [path, params]. If no route is generated the formatter will raise ActionController::UrlGenerationError
Register or
log in
to add new notes.
yaz -
August 19, 2014 - (v3.0.9 - v3.1.0)
yaz -
August 19, 2014 - (v3.0.9 - v3.1.0)
0 thanks
False query string parameters removed
This method is used in url_for (therefore in redirects as well).
If you pass a query string parameter to a url route that is false, before Rails 3.1, the generate method would reject it.
This causes issues on the redirected page if you are depending on the param to be have a specific value.
In Rails 3.2 they remove params.reject! {|k,v| !v.to_param} altogether.
So every single param you send is a string.
