anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-21 17:56:33 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Locale-dependent date formatting causes inconsistency #8661

New Issue
Open
opened 2026-02-16 18:10:31 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:10:31 -05:00
Owner
Copy Link
Copy Source

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

Originally assigned to: @rekram1-node on GitHub.

Problem

The codebase currently uses locale-dependent date formatting via toLocaleDateString() without specifying a locale, leading to inconsistent date representations across different systems and regions.

Examples of Inconsistency

  • US locale: 2/4/2026 (MM/DD/YYYY)
  • European locale: 4/2/2026 (DD/MM/YYYY)
  • ISO 8601: 2026-02-04 (YYYY-MM-DD)

This ambiguity makes dates unclear and problematic for:

  • Data exchange and API responses
  • Log parsing and analysis
  • Sorting and comparing dates
  • International users

Expected Behavior

Dates should be formatted consistently using the ISO 8601 standard (YYYY-MM-DD) which is:

  • Internationally recognized: Removes ambiguity between US and European formats
  • Lexicographically sortable: YYYY-MM-DD sorts correctly as strings
  • Unambiguous: Clear year-month-day order
  • Machine-friendly: Better for data interchange

Proposed Solution

Update Locale.datetime() in packages/opencode/src/util/locale.ts to use the en-CA locale for toLocaleDateString(), which outputs dates in YYYY-MM-DD format (ISO 8601).

Impact

  • Improves consistency across the application
  • Better user experience for international users
  • Safer date handling in APIs and data storage
  • Easier date parsing and manipulation
Originally created by @scarf005 on GitHub (Feb 5, 2026). Originally assigned to: @rekram1-node on GitHub. ## Problem The codebase currently uses locale-dependent date formatting via `toLocaleDateString()` without specifying a locale, leading to inconsistent date representations across different systems and regions. ## Examples of Inconsistency - **US locale**: 2/4/2026 (MM/DD/YYYY) - **European locale**: 4/2/2026 (DD/MM/YYYY) - **ISO 8601**: 2026-02-04 (YYYY-MM-DD) This ambiguity makes dates unclear and problematic for: - Data exchange and API responses - Log parsing and analysis - Sorting and comparing dates - International users ## Expected Behavior Dates should be formatted consistently using the ISO 8601 standard (YYYY-MM-DD) which is: - **Internationally recognized**: Removes ambiguity between US and European formats - **Lexicographically sortable**: YYYY-MM-DD sorts correctly as strings - **Unambiguous**: Clear year-month-day order - **Machine-friendly**: Better for data interchange ## Proposed Solution Update `Locale.datetime()` in `packages/opencode/src/util/locale.ts` to use the `en-CA` locale for `toLocaleDateString()`, which outputs dates in YYYY-MM-DD format (ISO 8601). ## Impact - Improves consistency across the application - Better user experience for international users - Safer date handling in APIs and data storage - Easier date parsing and manipulation
yindo commented 2026-02-16 18:10:31 -05:00
Author
Owner
Copy Link
Copy Source

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

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

  • #12398: feat: standardize date format to ISO 8601

Both issues address the exact same problem of locale-dependent date formatting and propose the same solution (using en-CA locale for ISO 8601 format output). Feel free to ignore if this addresses a different aspect.

@github-actions[bot] commented on GitHub (Feb 5, 2026): This issue might be a duplicate of existing issues. Please check: - #12398: feat: standardize date format to ISO 8601 Both issues address the exact same problem of locale-dependent date formatting and propose the same solution (using en-CA locale for ISO 8601 format output). Feel free to ignore if this addresses a different aspect.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8661
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?