Enable Disputes Feature in Release Builds

[AndreaDiazCorreia]

Removed debug-only restrictions from the disputes functionality. The disputes tab, swipe gestures, and chat interface are now fully available in release builds, allowing users to access dispute resolution features in production.

Summary by CodeRabbit

• Bug Fixes

  • Improved tab switching gestures for consistent behavior across all interactions.
  • Ensured tab descriptions always display properly.

• Refactor

  • Streamlined chat interface logic for better performance and stability.
  • Unified content display and removed debug-only code paths.

[coderabbitai]

Walkthrough

Refactored chat rooms list UI by removing debug-mode conditional branches and consolidating logic into unified code paths. Tab rendering, content display, and horizontal swipe gestures now execute unconditionally based on current tab state. Removed obsolete _buildMessagesTabHeader method and cleaned up imports.

Changes

Cohort / File(s)	Summary
Chat UI refactoring lib/features/chat/screens/chat_rooms_list.dart	Removed debug-mode branching; always render ChatTabs and display tab descriptions via _getTabDescription. Unified gesture handling to always detect horizontal swipes for tab switching. Consolidated content area into single GestureDetector wrapping _buildBody or DisputesList based on tab state. Deleted _buildMessagesTabHeader method. Removed unused import.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Verify that consolidating debug-mode conditionals preserves intended behavior for both messages and disputes tabs
• Confirm gesture handling for tab switching works correctly with unified GestureDetector wrapper
• Check that _getTabDescription covers all tab state scenarios previously handled by removed method
• Ensure import removal doesn't break any transitive dependencies

Poem

🐰 Debug branches trimmed, gestures unified and clean,
One path forward where conditionals had been,
Tab logic flows bright, no fork in the road,
Lighter and swifter, less burden to load! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "Enable Disputes Feature in Release Builds" directly aligns with the main objective described in the PR summary and the changes shown in the raw summary. The primary change involves removing debug-mode restrictions (kDebugMode branches) from the disputes functionality so that the disputes tab, swipe gestures, and chat interface are now available in production/release builds. The title is clear, specific, and concise—it accurately conveys what is being enabled and in what context, without vague or extraneous wording.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch andrea/fix-disputes-release

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

lib/features/chat/screens/chat_rooms_list.dart (2)

54-55: LGTM! Disputes feature now available in release builds.

The unconditional rendering of ChatTabs successfully enables the disputes tab in production. The implementation is clean and aligns with the PR objective.

Optional: Add trailing comma for formatter consistency.

Consider adding a trailing comma after the ChatTabs constructor for consistency with Dart formatter conventions:

-                ChatTabs(currentTab: currentTab),
+                ChatTabs(currentTab: currentTab),

(Note: This should be automatically handled by running flutter format.)

---

78-96: LGTM! Gesture-based navigation now enabled in production.

The horizontal swipe gesture detection is properly implemented and successfully enables users to navigate between messages and disputes tabs in release builds. The logic correctly handles left/right swipes.

Optional: Simplify the null check logic.

The primaryVelocity null check is repeated in both conditions. Consider extracting it for improved readability:

 onHorizontalDragEnd: (details) {
-  if (details.primaryVelocity != null &&
-      details.primaryVelocity! < 0) {
-    // Swipe left - go to disputes
-    ref.read(chatTabProvider.notifier).state = ChatTabType.disputes;
-  } else if (details.primaryVelocity != null &&
-      details.primaryVelocity! > 0) {
-    // Swipe right - go to messages
-    ref.read(chatTabProvider.notifier).state = ChatTabType.messages;
-  }
+  final velocity = details.primaryVelocity;
+  if (velocity == null) return;
+  
+  if (velocity < 0) {
+    // Swipe left - go to disputes
+    ref.read(chatTabProvider.notifier).state = ChatTabType.disputes;
+  } else if (velocity > 0) {
+    // Swipe right - go to messages
+    ref.read(chatTabProvider.notifier).state = ChatTabType.messages;
+  }
 },

Also, add a trailing comma after const DisputesList() on line 94 for formatter consistency.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b872221 and 2187e25.

📒 Files selected for processing (1)

• lib/features/chat/screens/chat_rooms_list.dart (3 hunks)

🧰 Additional context used

📓 Path-based instructions (4)

lib/features/**

📄 CodeRabbit inference engine (AGENTS.md)

Place application feature code under lib/features//, grouped by domain

Files:

• lib/features/chat/screens/chat_rooms_list.dart

**/*.dart

📄 CodeRabbit inference engine (AGENTS.md)

**/*.dart: Use Dart formatter defaults (two-space indentation, trailing commas) and run flutter format before committing
Resolve all Flutter analyzer warnings (flutter analyze must be clean)

**/*.dart: Remove unused imports and unused dependencies
Do not add // ignore: must_be_immutable to classes within generated files; rely on regeneration and existing file-level ignores

Files:

• lib/features/chat/screens/chat_rooms_list.dart

lib/**/*.dart

📄 CodeRabbit inference engine (AGENTS.md)

Name Riverpod providers as Provider or Notifier

lib/**/*.dart: Always use localized strings via S.of(context)!.keyName; avoid hardcoded user-facing text
Use clear, concise English for variable names, function names, and code comments; all comments must be in English
Target zero flutter analyze issues
Use latest Flutter/Dart APIs (e.g., Color.withValues() instead of withOpacity())
After async operations, check mounted before using BuildContext
Use const constructors where possible

Files:

• lib/features/chat/screens/chat_rooms_list.dart

lib/**/screens/**/*.dart

📄 CodeRabbit inference engine (CLAUDE.md)

Pass BuildContext to methods that need localization (S.of(context)!.keyName usage)

Files:

• lib/features/chat/screens/chat_rooms_list.dart

🔇 Additional comments (1)

lib/features/chat/screens/chat_rooms_list.dart (1)

69-69: LGTM! Description logic properly unified.

The unconditional use of _getTabDescription correctly handles both messages and disputes tabs. The implementation is clean and maintains proper localization support.

[Catrya]

tACK