If I do good can I eventually get a biscuit - aka get it into core (where someone with mad chops might clean it up), somewhere post 1.2? ;)
My only problem with the plugin is it definitely requires the tiny patches from tickets 6412 and 6413, and I'd rather not have to overwrite the whole ActiveRecordHelper.form() function in my plugin. While I understand these sort of things being a low priority right now, anyone have better idea how I should do that? Make a patchfile for the two of them and include it with the plug-in? That sort of feels user-unfriendly and might limit it to the hard-core. Maybe have an option to overwrite by default, but include the patch as an alternative? On a separate note - testing that matches (except I changed test_should_show_resourcename to test_should_get_show, to be consistent with the other test_should_get_action tests) the tests created by the generator script is almost done. After that I'll ask for review/criticism while I work on the docs. What then? Make a ticket patch and point it at my plug-in? Tim On 10/19/06, DHH <[EMAIL PROTECTED]> wrote: > > > DHH, what's the policy on changing default behavior in Rails 1.2? > > Absolutely forbidden, or only if there's a really big win? > > The ship has sailed on making these kind of changes for Rails 1.2. > We're in final crunch mode for release. Plugins are a good way to play > with this first in any case. > > > > > -- ..do you know why George Bush is so pissed off at Arabs? They brought us algebra. --Kurt Vonnegut --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core -~----------~----~----~----~------~----~------~--~---
