This project is archived and is in readonly mode.
Time with zone json exportation format
Reported by Damien MATHIEU | January 19th, 2010 @ 01:04 PM
The TimeWithZone json exportation can have two different
formats.
The standard json format. And the Active Support legacy format.
By default, the standard json format is used (which seems
logical).
But the tests doesn't reflects this. The non-standard one fails
because it expects the standard one to be the default one.
That's what I suggest to correct in this patch. So the test what's to be expected is obtained and the test passes.
Comments and changes to this ticket
-
Damien MATHIEU January 28th, 2010 @ 06:49 PM
This has just been corrected.
http://github.com/rails/rails/commit/d58398c2b5e98aad18dc72790230f3...
So this ticket can be closed. -
Rohit Arondekar June 15th, 2010 @ 12:13 PM
- State changed from “new” to “resolved”
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
Damien MATHIEU
Jeremy Kemper
Rohit Arondekar