Fix ActiveSupport::TimeWithZone#in#26597
Fix ActiveSupport::TimeWithZone#in#26597pixeltrix merged 1 commit intorails:masterfrom tbalthazar:26580
Conversation
|
Thanks for the pull request, and welcome! The Rails team is excited to review your changes, and you should hear from @matthewd (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. This repository is being automatically checked for code quality issues using Code Climate. You can see results for this analysis in the PR status below. Newly introduced issues should be fixed before a Pull Request is considered ready to review. Please see the contribution instructions for more information. |
|
@tbalthazar code is 👍 but can I just ask for a couple of things:
Thanks ❤️ |
Previously calls to `in` were being sent to the non-DST aware
method `Time#since` via `method_missing`. It is now aliased to
the DST aware `ActiveSupport::TimeWithZone#+` which handles
transitions across DST boundaries, e.g:
Time.zone = "US/Eastern"
t = Time.zone.local(2016,11,6,1)
# => Sun, 06 Nov 2016 01:00:00 EDT -05:00
t.in(1.hour)
# => Sun, 06 Nov 2016 01:00:00 EST -05:00
|
@pixeltrix Great suggestion, your changelog entry is better written, thanks! |
|
@tbalthazar restarted the Travis jobs 👍 |
Summary
ActiveSupport::TimeWithZone#inis now an alias forActiveSupport::TimeWithZone#+instead of being sent to aTimeinstance (viamethod_missing). It no longer returns wrong data when used on aTimeWithZonenear DST.Example wrong data that was returned before the fix:
It fixes #26580.