Rails - Aug 2012 - How do I force link_to/form helpers to use the superclass name in the path instead subclass?

I want my helpers to generate paths using a superclass instead of the 
subclasses. Assuming I have Owner and Member that both inherit from User, 
rails will use the current objects class name when generating paths:

Let''s say current_user is a mod: <%= link_to current_user.name, 
current_user %> will generate "/mod/:id". I want to force it to
generate
"/user/:id" regardless of the subclass.

I can name the path:
<%= link_to current_user.name, user_path(current_user) %>

But I still want to use the convenience of just passing the object:
<%= link_to current_user.name, current_user %>

Is this possible?


-- 
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
To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/EyihglN5e3cJ.
For more options, visit https://groups.google.com/groups/opt_out.

On Tuesday, August 7, 2012 11:13:56 AM UTC-5, Mohamad El-Husseini
wrote:
>
> I want my helpers to generate paths using a superclass instead of the 
> subclasses. Assuming I have Owner and Member that both inherit from User, 
> rails will use the current objects class name when generating paths:
>
> Let''s say current_user is a mod: <%= link_to current_user.name,
> current_user %> will generate "/mod/:id". I want to force it
to generate
> "/user/:id" regardless of the subclass.
>
> I can name the path:
> <%= link_to current_user.name, user_path(current_user) %>
>
> But I still want to use the convenience of just passing the object:
> <%= link_to current_user.name, current_user %>
>
> Is this possible?
>
>
You didn''t specify the rails version, but I''m pretty sure the
answer is no.
 In Rails 2.3.14 your link to is eventually calling url_for, which calls 
polymorphic_url (through polymorphic_path) since you''re not passing it
a
String, Hash or the symbol :back (
https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_view/helpers/url_helper.rb#L76).
 In turn that eventually calls build_named_route_call, which uses 
RecordIdentifier.plural_class_name(current_user), which is returning the 
class name (
https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_controller/polymorphic_routes.rb#L154).
 And finally that in turn eventually calls current_user.model_name (
https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_controller/record_identifier.rb#L100
)

You could look into overriding what model name returns for those classes, 
but that seems really far reaching and dangerous.  I''d just use the
path
helper since that best represents what you want to do, which is send an 
Owner or Member object not to /owners/:id or /members/:id but to /users/:id 
instead; ergo the verbosity doesn''t seem bad to me, it helps clarify.

As an alternative, you could also define the /owners/:id and /members/:id 
routes and point them at UsersController; not sure if that''s okay to
have
the extra routes, but that allows you to keep your shorthand notation, has 
that map to the expected URL, but lets you DRY the underlying controller 
class.

\Peter


-- 
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
To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/OEWb_1L040cJ.
For more options, visit https://groups.google.com/groups/opt_out.

I''m using Rails 3.2. And I''m pretty sure you can. Basically,
to get a form
to post to the right model I need to set it up generically. My initial form 
was:

= simple_form_for @user do |f|

To make it work I had to change it to this:

= simple_form_for :user, url: user_path(@user) do |f|

To work with link helpers, I added this as resource:

resources :owners, path: ''users'', controller:
''users''


On Wednesday, August 8, 2012 10:43:47 AM UTC-4, Peter
wrote:
>
> On Tuesday, August 7, 2012 11:13:56 AM UTC-5, Mohamad El-Husseini wrote:
>>
>> I want my helpers to generate paths using a superclass instead of the 
>> subclasses. Assuming I have Owner and Member that both inherit from
User,
>> rails will use the current objects class name when generating paths:
>>
>> Let''s say current_user is a mod: <%= link_to
current_user.name,
>> current_user %> will generate "/mod/:id". I want to force
it to generate
>> "/user/:id" regardless of the subclass.
>>
>> I can name the path:
>> <%= link_to current_user.name, user_path(current_user) %>
>>
>> But I still want to use the convenience of just passing the object:
>> <%= link_to current_user.name, current_user %>
>>
>> Is this possible?
>>
>>
> You didn''t specify the rails version, but I''m pretty sure
the answer is
> no.  In Rails 2.3.14 your link to is eventually calling url_for, which 
> calls polymorphic_url (through polymorphic_path) since you''re not
passing
> it a String, Hash or the symbol :back (
>
https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_view/helpers/url_helper.rb#L76).
>  In turn that eventually calls build_named_route_call, which uses 
> RecordIdentifier.plural_class_name(current_user), which is returning the 
> class name (
>
https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_controller/polymorphic_routes.rb#L154).
>  And finally that in turn eventually calls current_user.model_name (
>
https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_controller/record_identifier.rb#L100
> )
>
> You could look into overriding what model name returns for those classes, 
> but that seems really far reaching and dangerous.  I''d just use
the path
> helper since that best represents what you want to do, which is send an 
> Owner or Member object not to /owners/:id or /members/:id but to /users/:id
> instead; ergo the verbosity doesn''t seem bad to me, it helps
clarify.
>
> As an alternative, you could also define the /owners/:id and /members/:id 
> routes and point them at UsersController; not sure if that''s okay
to have
> the extra routes, but that allows you to keep your shorthand notation, has 
> that map to the expected URL, but lets you DRY the underlying controller 
> class.
>
> \Peter
>
>
>
-- 
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
To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/-NUfQAxSGDMJ.
For more options, visit https://groups.google.com/groups/opt_out.

It''s simple. Use AR::Base#becomes


Dheeraj Kumar


On Thursday 9 August 2012 at 12:20 AM, Mohamad El-Husseini wrote:
> I''m using Rails 3.2. And I''m pretty sure you can.
Basically, to get a form to post to the right model I need to set it up
generically. My initial form was:
> 
> = simple_form_for @user do |f|
> 
> To make it work I had to change it to this:
> 
> 
> = simple_form_for :user, url: user_path(@user) do |f|
> To work with link helpers, I added this as resource:
> 
> resources :owners, path: ''users'', controller:
''users''
> 
> 
> 
> 
> 
> On Wednesday, August 8, 2012 10:43:47 AM UTC-4, Peter wrote:
> > On Tuesday, August 7, 2012 11:13:56 AM UTC-5, Mohamad El-Husseini
wrote:
> > > I want my helpers to generate paths using a superclass instead of
the subclasses. Assuming I have Owner and Member that both inherit from User,
rails will use the current objects class name when generating paths:
> > > 
> > > Let''s say current_user is a mod: <%= link_to
current_user.name (http://current_user.name), current_user %> will generate
"/mod/:id". I want to force it to generate "/user/:id"
regardless of the subclass.
> > > 
> > > I can name the path:
> > > <%= link_to current_user.name (http://current_user.name),
user_path(current_user) %>
> > > 
> > > But I still want to use the convenience of just passing the
object:
> > > <%= link_to current_user.name (http://current_user.name),
current_user %>
> > > 
> > > 
> > > Is this possible?
> > > 
> > 
> > You didn''t specify the rails version, but I''m pretty
sure the answer is no.  In Rails 2.3.14 your link to is eventually calling
url_for, which calls polymorphic_url (through polymorphic_path) since
you''re not passing it a String, Hash or the symbol :back
(https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_view/helpers/url_helper.rb#L76).
In turn that eventually calls build_named_route_call, which uses
RecordIdentifier.plural_class_name(current_user), which is returning the class
name
(https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_controller/polymorphic_routes.rb#L154).
And finally that in turn eventually calls current_user.model_name
(https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_controller/record_identifier.rb#L100)
> > 
> > You could look into overriding what model name returns for those
classes, but that seems really far reaching and dangerous.  I''d just
use the path helper since that best represents what you want to do, which is
send an Owner or Member object not to /owners/:id or /members/:id but to
/users/:id instead; ergo the verbosity doesn''t seem bad to me, it helps
clarify.
> > 
> > As an alternative, you could also define the /owners/:id and
/members/:id routes and point them at UsersController; not sure if
that''s okay to have the extra routes, but that allows you to keep your
shorthand notation, has that map to the expected URL, but lets you DRY the
underlying controller class.
> > 
> > \Peter
> > 
> > 
> -- 
> 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
(mailto:rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org).
> To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe@googlegroups.com
(mailto:rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org).
> To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/-NUfQAxSGDMJ.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
-- 
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 https://groups.google.com/groups/opt_out.

Sorry, can you clarify your post a little? What does AR::Base#becomes 
exactly mean? I''m relatively new to some of this stuff!

On Wednesday, August 8, 2012 3:03:38 PM UTC-4, Dheeraj Kumar
wrote:
>
> It''s simple. Use AR::Base#becomes
>
>
> Dheeraj Kumar
>
> On Thursday 9 August 2012 at 12:20 AM, Mohamad El-Husseini wrote:
>
> I''m using Rails 3.2. And I''m pretty sure you can.
Basically, to get a form
> to post to the right model I need to set it up generically. My initial form
> was:
>
> = simple_form_for @user do |f|
>
> To make it work I had to change it to this:
>
> = simple_form_for :user, url: user_path(@user) do |f|
>
> To work with link helpers, I added this as resource:
>
> resources :owners, path: ''users'', controller:
''users''
>
>
> On Wednesday, August 8, 2012 10:43:47 AM UTC-4, Peter wrote:
>
> On Tuesday, August 7, 2012 11:13:56 AM UTC-5, Mohamad El-Husseini wrote:
>
> I want my helpers to generate paths using a superclass instead of the 
> subclasses. Assuming I have Owner and Member that both inherit from User, 
> rails will use the current objects class name when generating paths:
>
> Let''s say current_user is a mod: <%= link_to current_user.name,
> current_user %> will generate "/mod/:id". I want to force it
to generate
> "/user/:id" regardless of the subclass.
>
> I can name the path:
> <%= link_to current_user.name, user_path(current_user) %>
>
> But I still want to use the convenience of just passing the object:
> <%= link_to current_user.name, current_user %>
>
> Is this possible?
>
>
> You didn''t specify the rails version, but I''m pretty sure
the answer is
> no.  In Rails 2.3.14 your link to is eventually calling url_for, which 
> calls polymorphic_url (through polymorphic_path) since you''re not
passing
> it a String, Hash or the symbol :back (
>
https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_view/helpers/url_helper.rb#L76).
>  In turn that eventually calls build_named_route_call, which uses 
> RecordIdentifier.plural_class_name(current_user), which is returning the 
> class name (
>
https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_controller/polymorphic_routes.rb#L154).
>  And finally that in turn eventually calls current_user.model_name (
>
https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_controller/record_identifier.rb#L100
> )
>
> You could look into overriding what model name returns for those classes, 
> but that seems really far reaching and dangerous.  I''d just use
the path
> helper since that best represents what you want to do, which is send an 
> Owner or Member object not to /owners/:id or /members/:id but to /users/:id
> instead; ergo the verbosity doesn''t seem bad to me, it helps
clarify.
>
> As an alternative, you could also define the /owners/:id and /members/:id 
> routes and point them at UsersController; not sure if that''s okay
to have
> the extra routes, but that allows you to keep your shorthand notation, has 
> that map to the expected URL, but lets you DRY the underlying controller 
> class.
>
> \Peter
>
>
>  -- 
> 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
rubyonra...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>
> .
> To unsubscribe from this group, send email to 
> rubyonrails-ta...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
<javascript:>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/rubyonrails-talk/-/-NUfQAxSGDMJ.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
>  
>  
>  
-- 
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
To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/zS500RJNLR4J.
For more options, visit https://groups.google.com/groups/opt_out.

http://api.rubyonrails.org/classes/ActiveRecord/Persistence.html#method-i-becomes

class User < Person
end

u = User.first
u.class.name #=> User

p = u.becomes(Person)
p.class.name #=> Person



Dheeraj Kumar


On Thursday 9 August 2012 at 12:38 AM, Mohamad El-Husseini wrote:
> Sorry, can you clarify your post a little? What does AR::Base#becomes
exactly mean? I''m relatively new to some of this stuff!
> 
> On Wednesday, August 8, 2012 3:03:38 PM UTC-4, Dheeraj Kumar wrote:
> > It''s simple. Use AR::Base#becomes
> > 
> > 
> > Dheeraj Kumar
> > 
> > 
> > On Thursday 9 August 2012 at 12:20 AM, Mohamad El-Husseini wrote:
> > 
> > > I''m using Rails 3.2. And I''m pretty sure you
can. Basically, to get a form to post to the right model I need to set it up
generically. My initial form was:
> > > 
> > > = simple_form_for @user do |f|
> > > 
> > > To make it work I had to change it to this:
> > > 
> > > 
> > > = simple_form_for :user, url: user_path(@user) do |f|
> > > To work with link helpers, I added this as resource:
> > > 
> > > resources :owners, path: ''users'', controller:
''users''
> > > 
> > > 
> > > 
> > > 
> > > 
> > > On Wednesday, August 8, 2012 10:43:47 AM UTC-4, Peter wrote:
> > > > On Tuesday, August 7, 2012 11:13:56 AM UTC-5, Mohamad
El-Husseini wrote:
> > > > > I want my helpers to generate paths using a superclass
instead of the subclasses. Assuming I have Owner and Member that both inherit
from User, rails will use the current objects class name when generating paths:
> > > > > 
> > > > > Let''s say current_user is a mod: <%=
link_to current_user.name (http://current_user.name), current_user %> will
generate "/mod/:id". I want to force it to generate
"/user/:id" regardless of the subclass.
> > > > > 
> > > > > I can name the path:
> > > > > <%= link_to current_user.name
(http://current_user.name), user_path(current_user) %>
> > > > > 
> > > > > But I still want to use the convenience of just passing
the object:
> > > > > <%= link_to current_user.name
(http://current_user.name), current_user %>
> > > > > 
> > > > > 
> > > > > Is this possible?
> > > > > 
> > > > 
> > > > You didn''t specify the rails version, but
I''m pretty sure the answer is no.  In Rails 2.3.14 your link to is
eventually calling url_for, which calls polymorphic_url (through
polymorphic_path) since you''re not passing it a String, Hash or the
symbol :back
(https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_view/helpers/url_helper.rb#L76).
In turn that eventually calls build_named_route_call, which uses
RecordIdentifier.plural_class_name(current_user), which is returning the class
name
(https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_controller/polymorphic_routes.rb#L154).
And finally that in turn eventually calls current_user.model_name
(https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_controller/record_identifier.rb#L100)
> > > > 
> > > > You could look into overriding what model name returns for
those classes, but that seems really far reaching and dangerous.  I''d
just use the path helper since that best represents what you want to do, which
is send an Owner or Member object not to /owners/:id or /members/:id but to
/users/:id instead; ergo the verbosity doesn''t seem bad to me, it helps
clarify.
> > > > 
> > > > As an alternative, you could also define the /owners/:id and
/members/:id routes and point them at UsersController; not sure if
that''s okay to have the extra routes, but that allows you to keep your
shorthand notation, has that map to the expected URL, but lets you DRY the
underlying controller class.
> > > > 
> > > > \Peter
> > > > 
> > > > 
> > > -- 
> > > 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
rubyonra...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org (javascript:).
> > > To unsubscribe from this group, send email to
rubyonrails-ta...@googlegroups.com (javascript:).
> > > To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/-NUfQAxSGDMJ.
> > > For more options, visit https://groups.google.com/groups/opt_out.
> > >  
> > >  
> > 
> -- 
> 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
(mailto:rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org).
> To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe@googlegroups.com
(mailto:rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org).
> To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/zS500RJNLR4J.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
-- 
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 https://groups.google.com/groups/opt_out.

AR is activerecord
AR::Base is what all active record models inherit from
a#b means i''m talking about method b in class a



Dheeraj Kumar


On Thursday 9 August 2012 at 12:50 AM, Dheeraj Kumar wrote:
>
http://api.rubyonrails.org/classes/ActiveRecord/Persistence.html#method-i-becomes
> 
> class User < Person
> end
> 
> u = User.first
> u.class.name (http://u.class.name) #=> User
> 
> p = u.becomes(Person)
> p.class.name (http://p.class.name) #=> Person
> 
> 
> 
> Dheeraj Kumar
> 
> 
> On Thursday 9 August 2012 at 12:38 AM, Mohamad El-Husseini wrote:
> 
> > Sorry, can you clarify your post a little? What does AR::Base#becomes
exactly mean? I''m relatively new to some of this stuff!
> > 
> > On Wednesday, August 8, 2012 3:03:38 PM UTC-4, Dheeraj Kumar wrote:
> > > It''s simple. Use AR::Base#becomes
> > > 
> > > 
> > > Dheeraj Kumar
> > > 
> > > 
> > > On Thursday 9 August 2012 at 12:20 AM, Mohamad El-Husseini wrote:
> > > 
> > > > I''m using Rails 3.2. And I''m pretty sure
you can. Basically, to get a form to post to the right model I need to set it up
generically. My initial form was:
> > > > 
> > > > = simple_form_for @user do |f|
> > > > 
> > > > To make it work I had to change it to this:
> > > > 
> > > > 
> > > > = simple_form_for :user, url: user_path(@user) do |f|
> > > > To work with link helpers, I added this as resource:
> > > > 
> > > > resources :owners, path: ''users'',
controller: ''users''
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > On Wednesday, August 8, 2012 10:43:47 AM UTC-4, Peter wrote:
> > > > > On Tuesday, August 7, 2012 11:13:56 AM UTC-5, Mohamad
El-Husseini wrote:
> > > > > > I want my helpers to generate paths using a
superclass instead of the subclasses. Assuming I have Owner and Member that both
inherit from User, rails will use the current objects class name when generating
paths:
> > > > > > 
> > > > > > Let''s say current_user is a mod: <%=
link_to current_user.name (http://current_user.name), current_user %> will
generate "/mod/:id". I want to force it to generate
"/user/:id" regardless of the subclass.
> > > > > > 
> > > > > > I can name the path:
> > > > > > <%= link_to current_user.name
(http://current_user.name), user_path(current_user) %>
> > > > > > 
> > > > > > But I still want to use the convenience of just
passing the object:
> > > > > > <%= link_to current_user.name
(http://current_user.name), current_user %>
> > > > > > 
> > > > > > 
> > > > > > Is this possible?
> > > > > > 
> > > > > 
> > > > > You didn''t specify the rails version, but
I''m pretty sure the answer is no.  In Rails 2.3.14 your link to is
eventually calling url_for, which calls polymorphic_url (through
polymorphic_path) since you''re not passing it a String, Hash or the
symbol :back
(https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_view/helpers/url_helper.rb#L76).
In turn that eventually calls build_named_route_call, which uses
RecordIdentifier.plural_class_name(current_user), which is returning the class
name
(https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_controller/polymorphic_routes.rb#L154).
And finally that in turn eventually calls current_user.model_name
(https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_controller/record_identifier.rb#L100)
> > > > > 
> > > > > You could look into overriding what model name returns
for those classes, but that seems really far reaching and dangerous. 
I''d just use the path helper since that best represents what you want
to do, which is send an Owner or Member object not to /owners/:id or
/members/:id but to /users/:id instead; ergo the verbosity doesn''t seem
bad to me, it helps clarify.
> > > > > 
> > > > > As an alternative, you could also define the
/owners/:id and /members/:id routes and point them at UsersController; not sure
if that''s okay to have the extra routes, but that allows you to keep
your shorthand notation, has that map to the expected URL, but lets you DRY the
underlying controller class.
> > > > > 
> > > > > \Peter
> > > > > 
> > > > > 
> > > > -- 
> > > > 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
rubyonra...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org (javascript:).
> > > > To unsubscribe from this group, send email to
rubyonrails-ta...@googlegroups.com (javascript:).
> > > > To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/-NUfQAxSGDMJ.
> > > > For more options, visit
https://groups.google.com/groups/opt_out.
> > > >  
> > > >  
> > > 
> > -- 
> > 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
(mailto:rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org).
> > To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
(mailto:rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org).
> > To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/zS500RJNLR4J.
> > For more options, visit https://groups.google.com/groups/opt_out.
> >  
> >  
> 
-- 
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 https://groups.google.com/groups/opt_out.

OK, thanks. But why would I do this instead of just adding the extra 
resource?

resources :users
resources :owners, controller: ''users'', path:
''users''

And in forms I could just call "form_for :user" instead of
"form_for @user"?

On Wednesday, August 8, 2012 3:23:10 PM UTC-4, Dheeraj Kumar
wrote:
>
> AR is activerecord
> AR::Base is what all active record models inherit from
> a#b means i''m talking about method b in class a
>
>
> Dheeraj Kumar
>
> On Thursday 9 August 2012 at 12:50 AM, Dheeraj Kumar wrote:
>
>  
>
http://api.rubyonrails.org/classes/ActiveRecord/Persistence.html#method-i-becomes
>
> class User < Person
> end
>
> u = User.first
> u.class.name #=> User
>
> p = u.becomes(Person)
> p.class.name #=> Person
>
>
> Dheeraj Kumar
>
> On Thursday 9 August 2012 at 12:38 AM, Mohamad El-Husseini wrote:
>
> Sorry, can you clarify your post a little? What does AR::Base#becomes 
> exactly mean? I''m relatively new to some of this stuff!
>
> On Wednesday, August 8, 2012 3:03:38 PM UTC-4, Dheeraj Kumar wrote:
>
> It''s simple. Use AR::Base#becomes
>
>
> Dheeraj Kumar
>
> On Thursday 9 August 2012 at 12:20 AM, Mohamad El-Husseini wrote:
>
> I''m using Rails 3.2. And I''m pretty sure you can.
Basically, to get a form
> to post to the right model I need to set it up generically. My initial form
> was:
>
> = simple_form_for @user do |f|
>
> To make it work I had to change it to this:
>
> = simple_form_for :user, url: user_path(@user) do |f|
>
> To work with link helpers, I added this as resource:
>
> resources :owners, path: ''users'', controller:
''users''
>
>
> On Wednesday, August 8, 2012 10:43:47 AM UTC-4, Peter wrote:
>
> On Tuesday, August 7, 2012 11:13:56 AM UTC-5, Mohamad El-Husseini wrote:
>
> I want my helpers to generate paths using a superclass instead of the 
> subclasses. Assuming I have Owner and Member that both inherit from User, 
> rails will use the current objects class name when generating paths:
>
> Let''s say current_user is a mod: <%= link_to current_user.name,
> current_user %> will generate "/mod/:id". I want to force it
to generate
> "/user/:id" regardless of the subclass.
>
> I can name the path:
> <%= link_to current_user.name, user_path(current_user) %>
>
> But I still want to use the convenience of just passing the object:
> <%= link_to current_user.name, current_user %>
>
> Is this possible?
>
>
> You didn''t specify the rails version, but I''m pretty sure
the answer is
> no.  In Rails 2.3.14 your link to is eventually calling url_for, which 
> calls polymorphic_url (through polymorphic_path) since you''re not
passing
> it a String, Hash or the symbol :back (
>
https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_view/helpers/url_helper.rb#L76).
>  In turn that eventually calls build_named_route_call, which uses 
> RecordIdentifier.plural_class_name(current_user), which is returning the 
> class name (
>
https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_controller/polymorphic_routes.rb#L154).
>  And finally that in turn eventually calls current_user.model_name (
>
https://github.com/rails/rails/blob/v2.3.14/actionpack/lib/action_controller/record_identifier.rb#L100
> )
>
> You could look into overriding what model name returns for those classes, 
> but that seems really far reaching and dangerous.  I''d just use
the path
> helper since that best represents what you want to do, which is send an 
> Owner or Member object not to /owners/:id or /members/:id but to /users/:id
> instead; ergo the verbosity doesn''t seem bad to me, it helps
clarify.
>
> As an alternative, you could also define the /owners/:id and /members/:id 
> routes and point them at UsersController; not sure if that''s okay
to have
> the extra routes, but that allows you to keep your shorthand notation, has 
> that map to the expected URL, but lets you DRY the underlying controller 
> class.
>
> \Peter
>
>
>  -- 
> 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
rubyonra...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To unsubscribe from this group, send email to 
> rubyonrails-ta...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/rubyonrails-talk/-/-NUfQAxSGDMJ.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
>  
>
>  -- 
> 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
rubyonra...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<javascript:>
> .
> To unsubscribe from this group, send email to 
> rubyonrails-ta...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
<javascript:>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/rubyonrails-talk/-/zS500RJNLR4J.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
>  
>
>   
>  
-- 
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
To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/X5CmDa1_0PoJ.
For more options, visit https://groups.google.com/groups/opt_out.

On Wednesday, August 8, 2012 1:50:06 PM UTC-5, Mohamad El-Husseini
wrote:
>
> To make it work I had to change it to this:
>
> = simple_form_for :user, url: user_path(@user) do |f|
>
>
I''m confused, i thought that is what you are trying to avoid?  I.e. you
don''t want to have to specify user_path(@user), you wanted to just have
@user and have it compute the path helper as user_path, instead of 
owner_path or member_path? In your solution you just put in user_path, 
which makes your question moot, no?
 
> To work with link helpers, I added this as resource:
>
> resources :owners, path: ''users'', controller:
''users''
>
>
Right, I didn''t spell out the code like you did, but this is "As
an
alternative, you could also define the /owners/:id and /members/:id routes 
and point them at UsersController".  As a note, with that set of routes 
defined you should be able to use your original form declaration:

= simple_form_for @user do |f|

 Because simple_form_for will eventually do url_for(@user) like link 
helpers and therefore as long as owners and members are routed it should 
work.

\Peter

-- 
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
To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/CCJpt_7jMZMJ.
For more options, visit https://groups.google.com/groups/opt_out.

On Wednesday, August 8, 2012 5:45:17 PM UTC-5, Mohamad El-Husseini
wrote:
>
> OK, thanks. But why would I do this instead of just adding the extra 
> resource?
>
> resources :users
> resources :owners, controller: ''users'', path:
''users''
>
The reason would be if you didn''t want to expose the urls:

/members/:id
/owners/:id

I.e. with those routes defined if @user is a member with ID 37 then:

link_to ''click here'', @user             # => goes to
''/members/37''
link_to ''click here'', user_path(@user)  # => goes to
''/users/37''

So if you just want to be able to do the first line and don''t care
about
the url, map the routes; if you want to exactly duplicate the second line 
(i.e. your original code, and what would technically have ''helpers to 
generate paths using a superclass instead of the subclasses'') then you 
could use becomes as such:

link_to ''click here'', @user.becomes(User)    # => goes to
''/users/37''

However, I personally think the one with user_path is more readable in this 
case.

\Peter

-- 
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
To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/18IyihvWIjUJ.
For more options, visit https://groups.google.com/groups/opt_out.