It will be a plugin eventually, so you can still use it as is, but you'll have to install a plugin when a later rails version is released.
The case you're speaking of is partially one reason why it will be a plugin; too many people want it to do different things and when that happens the functionality should remain as a plugin for a while (if not forever). On 10/2/06, Daniel N <[EMAIL PROTECTED]> wrote: > > > On 10/2/06, Michael Koziarski <[EMAIL PROTECTED]> wrote: > > > > > I guess I could also overwrite update_attribute to use validataion, but > why > > > was validation removed from this method in the first place? I don't > want to > > > go breaking things... > > > > Most of the other core guys are in bed right now, but I've never used > > the in place editor, and I share your surprise that it deliberately > > avoids validation. Perhaps David, Tobi, Thomas or Rick could chime > > in? On the other hand, it's been deprecated in trunk, so perhaps > > this is a good opportunity for someone to extract it to a plugin and > > make it much more robust and feature filled? > > Thanx for the feedback... I didn't realise it was depricated. That still > leaves the issue of update_attribute though. I guess I'll wait for other > guys. Thanx again for the feedback. > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
