Rails core - Jul 2007 - Render Partial Hash Collection: Bug-Tracker Insanity

This is a bug that was discovered two years ago.  However, every time
it''s mentioned on the tracker it gets "closed: wontfix" with
no
explanation of why!

http://dev.rubyonrails.org/ticket/4398
http://dev.rubyonrails.org/ticket/3096
http://dev.rubyonrails.org/ticket/2751

These tickets contain a clear explanation of the problem, and one
(http://dev.rubyonrails.org/ticket/2751) even seems to have a patch to
fix it.  So why wont they apply it?

I can''t imagine we''re still trying to be backwards compatible
with API
of two years ago, with all the deprecation warnings flying around.
Also, this is STILL not mentioned in the documentation for render
partial collection after two years.  And this is a feature I need to
use often, so throwing in a hack everywhere just makes things ugly.
Can anyone explain why they wont fix this bug?


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

> Can anyone explain why they wont fix this bug?
Please try and keep your tone productive, there''s no massive
conspiracy here, we''re all trying to achieve the same goals.  As was
mentioned in those patches from years ago, the behaviour couldn''t be
changed for backwards compatibility reasons.

This is indeed no longer the case,  so please do feel free to submit a
patch which fixes this in trunk.  I''d be more than happy to apply it.

-- 
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
-~----------~----~----~----~------~----~------~--~---

Notice some of those tickets were closed a month ago?  I don''t think
they want it to be fixed...  But if you can do it, sure, I''ll check
out the fixes and see how they work on trunk =].

On Jul 4, 1:47 pm, "Michael Koziarski" <mich...@koziarski.com>
wrote:
> > Can anyone explain why they wont fix this bug?
>
> Please try and keep your tone productive, there''s no massive
> conspiracy here, we''re all trying to achieve the same goals.  As
was
> mentioned in those patches from years ago, the behaviour couldn''t
be
> changed for backwards compatibility reasons.
>
> This is indeed no longer the case,  so please do feel free to submit a
> patch which fixes this in trunk.  I''d be more than happy to apply
it.
>
> --
> 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
-~----------~----~----~----~------~----~------~--~---

> Notice some of those tickets were closed a month ago?  I don''t
think
> they want it to be fixed...  But if you can do it, sure, I''ll
check
> out the fixes and see how they work on trunk =].
We have hundreds of bug reports, which have atrophied and they''ve been
closed, sometimes errantly.    Josh closed the ticket because it had
seen no action in a year, if you reopen it no one will close it again.


-- 
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
-~----------~----~----~----~------~----~------~--~---

Here we go http://dev.rubyonrails.org/ticket/8900

Cheers,
Pratik

On Jul 5, 12:59 am, "Michael Koziarski" <mich...@koziarski.com>
wrote:
> > Notice some of those tickets were closed a month ago?  I
don''t think
> > they want it to be fixed...  But if you can do it, sure, I''ll
check
> > out the fixes and see how they work on trunk =].
>
> We have hundreds of bug reports, which have atrophied and they''ve
been
> closed, sometimes errantly.    Josh closed the ticket because it had
> seen no action in a year, if you reopen it no one will close it again.
>
> --
> 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
-~----------~----~----~----~------~----~------~--~---