Repository navigation
cleanup(data): fix epoch ISO formatter KDoc - #1325
Conversation
epochToIso8601 formats milliseconds with kotlin.time.Instant.toString(): a UTC ISO-8601 instant ending in Z, with the fraction omitted on whole seconds and exactly three digits otherwise. The old KDoc still described a manual kotlinx-datetime formatter. Co-authored-by: Devil <9thLevelSoftware@users.noreply.github.com>
Code Review SummaryStatus: 2 Issues Found | Recommendation: Merge (suggestions only) Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (1 file)
VerdictApprove — doc-only change; the new KDoc matches Correctness / Safety FindingsNo correctness or safety findings. Ponytail Review
Ponytail net: -1 lines. Suggested Minimal PatchOptional, at most 2 files: (1) collapse Final Merge GuidanceCan merge as-is; both findings are optional cleanup. Note: no code was executed in this review. The whole-second output ( Fix these issues in Kilo Cloud Reviewed by minimax-m3 · Input: 60K · Output: 26.8K · Cached: 632.5K Review guidance: REVIEW.md from base branch |
Summary
epochToIso8601still documented a manual kotlinx-datetime conversion. After #1315 the function formats epoch milliseconds withkotlin.time.Instant.toString().The KDoc now matches that output: a UTC ISO-8601 instant that always ends in
Z. Whole seconds omit the fraction (2023-11-14T22:13:20Z); any other millisecond keeps exactly three fractional digits, including trailing zeros (2023-11-14T22:13:20.100Z).The matching test comment in
PortalSyncAdapterTest.ktalready nameskotlin.time.Instant.toString()and the2023-11-14T22:13:20Zexample, so it was left unchanged. No behavior change.Verify
./gradlew :shared:compileKotlinIosSimulatorArm64 -Pskip.supabase.check=true :shared:compileAndroidHostTest :androidApp:compileDebugKotlinBUILD SUCCESSFUL