Hi Mateo, On 05.05.2009, at 02:49, mateo murphy wrote: > 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?
I don't know of any such thing and I would be surprised if anybody removed previously added features right away without any discussion. But I find the relevant bits of code still the same and the i18n tests haven't changed a lot: http://github.com/rails/rails/blob/master/activerecord/lib/active_record/validations.rb http://github.com/rails/rails/commits/master/activerecord/test/cases/validations_i18n_test.rb Maybe you've been looking at the 3-0-unstable branch? According to http://weblog.rubyonrails.org/2009/4/13/one-giant-leap-forward currently master is used for 3.0 dev while 2.3.x dev takes place in 2-3-stable. Am I missing something? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
