diff options
author | Carlos Antonio da Silva <carlosantoniodasilva@gmail.com> | 2013-01-22 09:31:31 -0200 |
---|---|---|
committer | Carlos Antonio da Silva <carlosantoniodasilva@gmail.com> | 2013-01-22 09:31:31 -0200 |
commit | 6fcdcfe1e5fe8780f3c9c56bb4a0b7963f313e4e (patch) | |
tree | 7054249d47a72b5e2719df2c0b39692df387d801 /Rakefile | |
parent | b45c63b8c0d8e8e92207c2d049a5d764aa12a39d (diff) | |
download | rails-6fcdcfe1e5fe8780f3c9c56bb4a0b7963f313e4e.tar.gz rails-6fcdcfe1e5fe8780f3c9c56bb4a0b7963f313e4e.tar.bz2 rails-6fcdcfe1e5fe8780f3c9c56bb4a0b7963f313e4e.zip |
Revert "Merge pull request #7873 from steveklabnik/update_initializer"
This reverts commit 43e14f8ff203c21646f733d35bdde4e68da70a3b, reversing
changes made to bb17a0f085aba40a1952612f6c98b2a5804a1152.
Conflicts:
railties/lib/rails/generators/rails/app/templates/config/application.rb
railties/lib/rails/generators/rails/app/templates/config/initializers/locale.rb
Reason: setting the Time.zone in an after_initialize block can become a
problem for people upgrading, since it's not going to be available when
config/initializers run, and people might be relying on it.
An example that I noticed was with the Chronic gem, for date/time parsing.
It requires us to configure the time class to be Time.zone, and doing
that in an initializer no longer worked with these changes, so reverting
is the safer path for now.
Diffstat (limited to 'Rakefile')
0 files changed, 0 insertions, 0 deletions