ConversationDetailProvider.conversation - No valid conversation crash

[aaravgarg]

Summary

• Add conversationOrNull getter that returns null instead of throwing StateError
• Add hasConversation convenience getter for safe existence checks
• The existing conversation getter still throws for callers that expect non-null, but callers can now safely check first
• Prevents crash when navigating to conversation detail for a date with no conversations

Crash Stats

• Events: 50 (iOS) + 58 (Android)
• Users affected: 9 (iOS) + 8 (Android)
• Crashlytics (iOS): View in Console
• Crashlytics (Android): View in Console

Test plan

• Verify conversation detail page still works normally
• Test navigating to a date with no conversations (should handle gracefully)

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request effectively addresses a crash that occurs when no conversation is available for a selected date. The changes in ConversationDetailProvider are well-designed: renaming the conversation getter to conversationOrNull and making it return null instead of throwing an error is a good pattern. The addition of the hasConversation getter provides a convenient and safe way for UI components to check for the existence of a conversation before attempting to access it. Preserving the original throwing behavior in the conversation getter ensures backward compatibility for existing code that relies on a non-null return value. The implementation is clean and directly solves the reported issue.