On Mon, May 4, 2009 at 11:56 AM, mateo murphy <mateo.mur...@gmail.com>wrote:
> > > I believe, that for a ground breaking 3.0 release a simple clean > > API and simple reliable implementation are more important than > > backward compatibility. > > > I agree that it's not the best solution, and that for 3.0 the API > should be rethought. However, I think that coming up with a simple > patch that supports the current API but allows people to do what they > need without monkeypatching is a very good idea in the short term. Ok, looking at the 3.0 validation code for the first time, I see that refactoring has already been started, and the previous API has been deprecated. Considering this, I don't think my proposal makes as much sense; if we're going to be changing the API anyway, we may as well do it properly. Also of note is that the previously deprecated default_error_messages is back, and generate_message is gone completely, I18n support along with it. Is anyone aware of any specific reason for this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "rails-i18n" group. To post to this group, send email to rails-i18n@googlegroups.com To unsubscribe from this group, send email to rails-i18n+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rails-i18n?hl=en -~----------~----~----~----~------~----~------~--~---
