Those look like legitimate bugs in implementation, rather than caused by confusion. I don't really see a point in extracting that functionality in a plugin, with hope of making a come back to core. If it's gets converted into a plugin, it should stay there, always.
Also, converting an edge functionality into a plugin because of defects in implementation, defeats the whole purpose of having edge at first place. I guess it's time to make a choice once and for all, if it's gonna be in core rails or not. My vote is to keep it in edge for points explained in posts above. Thanks, Pratik On 7/7/07, Josh Peek <[EMAIL PROTECTED]> wrote: > > > On Jul 7, 11:41 am, Pratik <[EMAIL PROTECTED]> wrote: > > Can you please point out to tickets related to the issue ? They'd > > surely provide a better insight to your point. > > Heres a few: [7152], #8725, #8782, #8719, #8720, #8705, #8830, #8654, > #8640 > > > > > -- http://m.onkey.org --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
