Conversation
A Rails application rendering a Time through `render json:` emits three decimal places, because ActiveSupport::JSON::Encoding.time_precision defaults to 3. The codec called Time#iso8601 with no argument, which emits none, so every date-time in a migrating application's responses silently changed shape and lost precision: master "2026-09-14T17:05:03.250Z" before "2026-09-14T17:05:03Z" Found migrating nexus-api, where it affected eight properties across wallet transactions, uploads, the onboarding checklist and vortex assets.
Collaborator
Author
|
Not proceeding — iso8601 without fractional seconds is fine as the gem's output. Recording the difference on the nexus-api migration instead. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Time#iso8601with no argument emits no decimal places. Rails'render json:emits three (ActiveSupport::JSON::Encoding.time_precision), so every date-time in an application migrating onto openapi_kit changed shape and lost precision.Found while verifying nexus-api's migration byte-for-byte against the old generator — it affected eight properties there. Decimal, uuid, float, integer and string already matched exactly.