In Ruby on Rails, routes.rb, if we create a "named route"
map.something ":a/:b", :controller =>
''foobar''
it will also create "something_path" and "something_url"
which are two
methods usable in the controller and in the view. Does "map.connect"
create something like that too? Otherwise, isn''t
"map.connect" somewhat
disadvantaged in this way? I checked that "connect_path" and
"connect_url" both aren''t created automatically.
--
Posted via http://www.ruby-forum.com/.
--
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
Frederick Cheung
2010-Jun-12 11:46 UTC
Re: map.connect will not create connect_path and connect_url?
On Jun 12, 12:11 pm, Jian Lin <li...-fsXkhYbjdPsEEoCn2XhGlw@public.gmane.org> wrote:> In Ruby on Rails, routes.rb, if we create a "named route" > > map.something ":a/:b", :controller => ''foobar'' > > it will also create "something_path" and "something_url" which are two > methods usable in the controller and in the view. Does "map.connect" > create something like that too? Otherwise, isn''t "map.connect" somewhat > disadvantaged in this way? I checked that "connect_path" and > "connect_url" both aren''t created automatically.map.connect predates named routes. Fred> -- > Posted viahttp://www.ruby-forum.com/.-- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.