Rails core - Mar 2007 - simply_helpful's form_for not respecting default_url_options (only_path)

Looking over the discussions and Trac tickets am I correct in assuming
that the simply_helpful''s form_for not respecting the
default_url_options (specifically only_path) is a side-effect of some
other default behavior choices?

Personally, I set only_path to true as my default as I think except
were you are dealing with https it makes life much easier (especially
in testing) and is just cleaner all around.  I''ve always hated
unneccessarily qualified links, as they can bite you in the ass.

If I could track down and modify this behavior, would there be enough
interest in it (it may be right at the edge of my ruby-fu) to get it
patched in?  I know the usual answer is "make a plugin," but I
don''t
know if I really would want to maintain a plugin for a plugin.


--~--~---------~--~----~------------~-------~--~----~
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-core@googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-core-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---

> If I could track down and modify this behavior, would there be enough
> interest in it (it may be right at the edge of my ruby-fu) to get it
> patched in?  I know the usual answer is "make a plugin," but I
don''t
> know if I really would want to maintain a plugin for a plugin.
Sure,  if you can track something down, and it doesn''t break other
behaviour, there''s no reason it can''t go in.


-- 
Cheers

Koz

--~--~---------~--~----~------------~-------~--~----~
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-core@googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-core-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---

I''ll see what I can do ;)

On Mar 15, 2:17 pm, "Michael Koziarski" <mich...@koziarski.com>
wrote:
> > If I could track down and modify this behavior, would there be enough
> > interest in it (it may be right at the edge of my ruby-fu) to get it
> > patched in?  I know the usual answer is "make a plugin," but
I don''t
> > know if I really would want to maintain a plugin for a plugin.
>
> Sure,  if you can track something down, and it doesn''t break other
> behaviour, there''s no reason it can''t go in.
>
> --
> Cheers
>
> Koz

--~--~---------~--~----~------------~-------~--~----~
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-core@googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-core-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---