On May 23, 3:16 pm, Michael Koziarski wrote:
> > Shouldn't form_for be keying off of ":as => :thread" and using
> > threads_path/thread_path instead of forum_threads_path/
> > forum_thread_path ?
>
> No, not as currently designed and implemented. The mapping from
> instance to route helper name i
te:
> How about if you pass the :controller option to it as well as :as?
>
> On 24 May 2010 08:38, Jury wrote:
>
>
>
>
>
>
>
> > On May 23, 3:33 pm, Ryan Bigg wrote:
> > > As far as I know, this is what :as is for. I've never seen :class_name
>
On May 23, 3:33 pm, Ryan Bigg wrote:
> As far as I know, this is what :as is for. I've never seen :class_name used
> within the context of routes, but it may be an available option I don't know
> about.
It would appear that it renames the helper route methods, but not the
URLs that are actually
Thanks for the reply, Michael.
On May 23, 3:16 pm, Michael Koziarski wrote:
> > Shouldn't form_for be keying off of ":as => :thread" and using
> > threads_path/thread_path instead of forum_threads_path/
> > forum_thread_path ?
>
> No, not as currently designed and implemented. The mapping from
>
Hi Ryan,
I specify :class_name in the router so that I can generate URLs that
look like:
/thread
/thread/new
/thread/5/edit
etc
while having the requests dispatched to the ForumThreadController
(forum_thread_controller.rb).
Unfortunately, due to namespace constraints, I can't just call the
cont
Hi guys,
I've come across what I think is a bug in form_for in Rails 3 beta 3,
and just wanted to run it by you before I needlessly created a
ticket. Here's the situation:
Named route:
resources :thread, :class_name => "forum_thread"
Controller name:
forum_thread_controller
Model
.
-Jury
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rubyonrails-c...@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For mo
