kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity

[ci skip] Document millisecond precision change in ActiveSupport::TimeWithZone#as_json

Browse source
This commit is contained in:
Eugene Gilburg 2014-07-09 13:47:17 -07:00
parent 4c34ad37b2
commit d703fe5fff
1 changed files with 12 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
guides/source/upgrading_ruby_on_rails.md
View file

@ -241,6 +241,16 @@ If your application depends on one of these features, you can get them back by
adding the [`activesupport-json_encoder`](https://github.com/rails/activesupport-json_encoder)
gem to your Gemfile.
#### JSON representation of Time objects
`#as_json` for objects with time component (`Time`, `DateTime`, `ActiveSupport::TimeWithZone`)
now returns millisecond precision by default. If you need to keep old behavior with no millisecond
precision, set the following in an initializer:
```
ActiveSupport::JSON::Encoding.time_precision = 0
```
### Usage of `return` within inline callback blocks
Previously, Rails allowed inline callback blocks to use `return` this way:
@ -434,8 +444,8 @@ string keys consistently.
### Explicit block use for `ActiveSupport::Callbacks`
Rails 4.1 now expects an explicit block to be passed when calling
`ActiveSupport::Callbacks.set_callback`. This change stems from
Rails 4.1 now expects an explicit block to be passed when calling
`ActiveSupport::Callbacks.set_callback`. This change stems from
`ActiveSupport::Callbacks` being largely rewritten for the 4.1 release.
```ruby