Skip to content

fix: remove dead nil-coalescing on DateIntervalFormatter.string - #7

Merged
Lixeas merged 1 commit into
mainfrom
fix/date-interval-warning
Sep 25, 2026
Merged

Lixeas merged 1 commit into
mainfrom
fix/date-interval-warning

Conversation

@Lixeas

@Lixeas Lixeas commented Sep 25, 2026 •

Copy link
Copy Markdown
Owner

Summary

DateIntervalFormatter.string(from:to:) returns non-optional String (unlike DateFormatter.string(from:)), so ?? "" in billingCycleRange was dead code — flagged as a warning in a real Xcode build.

Test plan

  • swift build / swift test via the Test workflow (self-hosted runner)

🤖 Generated with Claude Code

DateIntervalFormatter.string(from:to:) returns non-optional String,
unlike DateFormatter.string(from:) -- the ?? "" was always dead code
(compiler warning caught in a real Xcode build).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Vag2FZvTekVg34kUeb791Q
@Lixeas
Lixeas merged commit 92199b2 into main Sep 25, 2026
1 check passed
Lixeas added a commit that referenced this pull request Sep 25, 2026
fix: remove dead nil-coalescing on DateIntervalFormatter.string
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant