feat: standardize date format to ISO 8601 #8662

Open
opened 2026-02-16 18:10:31 -05:00 by yindo · 2 comments
Owner

Originally created by @scarf005 on GitHub (Feb 5, 2026).

Originally assigned to: @thdxr on GitHub.

Problem

The codebase uses locale-dependent date formats which causes:

  • Inconsistency across different regions
  • Ambiguity between MM/DD/YYYY (US) and DD/MM/YYYY (European)
  • Non-sortable date strings
  • Interoperability issues

Solution

Standardize to ISO 8601 format (YYYY-MM-DD):

  • Update Locale.datetime() to use en-CA locale
  • Ensures consistent YYYY-MM-DD output

Benefits

  • Consistency: International standard
  • Sortability: Lexicographically sortable
  • Clarity: No ambiguity
  • Interoperability: Better for APIs and data exchange

Related: Reopening #6450

Originally created by @scarf005 on GitHub (Feb 5, 2026). Originally assigned to: @thdxr on GitHub. ## Problem The codebase uses locale-dependent date formats which causes: - Inconsistency across different regions - Ambiguity between MM/DD/YYYY (US) and DD/MM/YYYY (European) - Non-sortable date strings - Interoperability issues ## Solution Standardize to ISO 8601 format (YYYY-MM-DD): - Update `Locale.datetime()` to use `en-CA` locale - Ensures consistent YYYY-MM-DD output ## Benefits - **Consistency**: International standard - **Sortability**: Lexicographically sortable - **Clarity**: No ambiguity - **Interoperability**: Better for APIs and data exchange Related: Reopening #6450
Author
Owner

@github-actions[bot] commented on GitHub (Feb 5, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #6450: standardize date format to ISO 8601 (YYYY-MM-DD) - Previously closed, this appears to be reopening or re-addressing that work
  • #9025: Session timestamps display in UTC instead of local time - Related locale/timezone issues
  • #7208: Add option to use 24-hour time format in session view - Related time format customization
  • #9494: Updating a session's metadata ought not update the timestamp - Related timestamp handling concerns
  • #11606: Timezone-specific date display issues in usage costs (Asia/Singapore timezone)

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Feb 5, 2026): This issue might be a duplicate of existing issues. Please check: - #6450: standardize date format to ISO 8601 (YYYY-MM-DD) - Previously closed, this appears to be reopening or re-addressing that work - #9025: Session timestamps display in UTC instead of local time - Related locale/timezone issues - #7208: Add option to use 24-hour time format in session view - Related time format customization - #9494: Updating a session's metadata ought not update the timestamp - Related timestamp handling concerns - #11606: Timezone-specific date display issues in usage costs (Asia/Singapore timezone) Feel free to ignore if none of these address your specific case.
Author
Owner

@ariane-emory commented on GitHub (Feb 5, 2026):

This seems undesirable to me. I want OpenCode to format the dates in my country's date format, not in some other international format that I do not use.

@ariane-emory commented on GitHub (Feb 5, 2026): This seems undesirable to me. I want OpenCode to format the dates in _my_ country's date format, not in some other international format that I do not use.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8662