fix: Add back button

[alexrisch]

Added back button back for conversation screen

This was likely an issue with expo 52 upgrade and header changes happening at the same time

Summary by CodeRabbit

• Bug Fixes
  • Adjusted navigation header back button visibility to use default behavior.

[coderabbitai]

Walkthrough

The pull request involves a modification in the features/conversation/conversation.nav.tsx file, specifically in the ConversationNav function. The change relates to the back button's visibility setting, where the headerBackVisible: false line has been commented out. This alteration allows the default back button behavior to take effect, removing the previous explicit hiding of the navigation header's back button.

Changes

File	Change Summary
features/conversation/conversation.nav.tsx	Commented out headerBackVisible: false, enabling default back button visibility

Possibly related PRs

• fix: Navigating to chat from profile #1265: Modifications to navigation behavior, removing focus parameter from navigation calls
• fix: Fixed Conversation Updated messaging on conversation list #1450: Enhancements to messaging related to conversation updates

Suggested reviewers

• thierryskoda

Poem

🐰 A nav button's tale, once hidden from sight,
Now peeks out with newfound delight!
Commented code, a gentle reprieve,
Back button's freedom, we now perceive
Hop, hop, navigation's sweet flight! 🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bbe4a32 and 1835c5a.

📒 Files selected for processing (1)

• features/conversation/conversation.nav.tsx (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• features/conversation/conversation.nav.tsx

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: tsc
• GitHub Check: performance-test
• GitHub Check: lint
• GitHub Check: test

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Performance Comparison Report

• Current: c248486 - 2025-01-08 01:31:34Z
• Baseline: main (bbe4a32) - 2025-01-08 01:30:16Z

Significant Changes To Duration

There are no entries

Meaningless Changes To Duration

Show entries

Name	Type	Duration	Count
Avatar Image 10 runs	render	0.8 ms → 0.9 ms (+0.1 ms, +12.5%)	1 → 1
Avatar Image 50 runs	render	0.9 ms → 0.9 ms	1 → 1
Empty Avatar 10 runs	render	1.2 ms → 1.6 ms (+0.4 ms, +33.3%) 🔴	1 → 1
Empty Avatar 50 runs	render	1.2 ms → 1.1 ms (-0.1 ms, -5.1%)	1 → 1
Text Component with color prop - 10 runs	render	0.8 ms → 0.7 ms (-0.1 ms, -12.5%)	1 → 1
Text Component with default props - 10 runs	render	1.4 ms → 0.7 ms (-0.7 ms, -50.0%) 🟢	1 → 1
Text Component with translation key - 10 runs	render	0.8 ms → 0.6 ms (-0.2 ms, -25.0%) 🟢	1 → 1
Text Component with weight and size - 10 runs	render	0.4 ms → 0.6 ms (+0.2 ms, +50.0%) 🔴	1 → 1

Show details

Name	Type	Duration	Count
Avatar Image 10 runs	render	Baseline Mean: 0.8 ms Stdev: 0.4 ms (52.7%) Runs: 0 1 1 1 0 1 1 1 1 1 Warmup runs: 1 Current Mean: 0.9 ms Stdev: 0.3 ms (35.1%) Runs: 1 1 1 1 1 0 1 1 1 1 Warmup runs: 1	Baseline Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1 Render issues: Current Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1 Render issues:
Avatar Image 50 runs	render	Baseline Mean: 0.9 ms Stdev: 0.4 ms (40.8%) Runs: 1 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 1 1 1 1 0 1 1 1 1 1 1 0 1 0 1 1 1 1 1 1 1 1 1 1 1 1 1 0 1 1 1 1 Warmup runs: 1 Current Mean: 0.9 ms Stdev: 0.4 ms (47.0%) Runs: 0 1 0 1 1 1 1 2 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 1 1 1 1 1 1 1 1 1 1 0 1 1 1 0 1 1 1 0 1 0 1 1 1 1 1 Warmup runs: 1	Baseline Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Render issues: Current Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Render issues:
Empty Avatar 10 runs	render	Baseline Mean: 1.2 ms Stdev: 0.4 ms (35.1%) Runs: 1 1 2 1 1 1 1 1 1 2 Warmup runs: 2 Current Mean: 1.6 ms Stdev: 0.5 ms (32.3%) Runs: 2 1 2 1 2 2 2 1 1 2 Warmup runs: 3	Baseline Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1 Render issues: Current Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1 Render issues:
Empty Avatar 50 runs	render	Baseline Mean: 1.2 ms Stdev: 0.4 ms (32.9%) Runs: 1 1 1 1 1 1 2 2 1 1 1 1 1 2 2 1 1 1 2 1 1 1 1 1 1 1 1 1 2 1 1 2 1 1 1 2 1 1 2 1 1 1 1 1 1 1 1 1 1 1 Warmup runs: 1 Current Mean: 1.1 ms Stdev: 0.4 ms (38.9%) Runs: 2 1 1 1 1 1 1 1 2 1 1 1 1 1 1 1 1 1 1 1 0 1 1 2 1 1 2 2 1 0 1 1 1 1 1 1 2 2 1 1 1 1 1 1 1 1 1 2 1 1 Warmup runs: 1	Baseline Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Render issues: Current Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Render issues:
Text Component with color prop - 10 runs	render	Baseline Mean: 0.8 ms Stdev: 0.4 ms (52.7%) Runs: 1 1 0 1 1 1 1 1 1 0 Warmup runs: 0 Current Mean: 0.7 ms Stdev: 0.5 ms (69.0%) Runs: 0 1 1 1 0 1 1 1 1 0 Warmup runs: 0	Baseline Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1 Render issues: Current Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1 Render issues:
Text Component with default props - 10 runs	render	Baseline Mean: 1.4 ms Stdev: 0.7 ms (49.9%) Runs: 2 2 2 2 1 0 2 1 1 1 Warmup runs: 5 Current Mean: 0.7 ms Stdev: 0.5 ms (69.0%) Runs: 1 1 1 1 1 0 1 1 0 0 Warmup runs: 4	Baseline Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1 Render issues: Current Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1 Render issues:
Text Component with translation key - 10 runs	render	Baseline Mean: 0.8 ms Stdev: 0.4 ms (52.7%) Runs: 1 0 1 1 1 1 1 1 1 0 Warmup runs: 2 Current Mean: 0.6 ms Stdev: 0.5 ms (86.1%) Runs: 1 0 1 1 0 1 1 1 0 0 Warmup runs: 1	Baseline Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1 Render issues: Current Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1 Render issues:
Text Component with weight and size - 10 runs	render	Baseline Mean: 0.4 ms Stdev: 0.5 ms (129.1%) Runs: 0 1 1 0 0 1 0 1 0 0 Warmup runs: 1 Current Mean: 0.6 ms Stdev: 0.5 ms (86.1%) Runs: 1 1 0 0 1 0 1 0 1 1 Warmup runs: 1	Baseline Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1 Render issues: Current Mean: 1 Stdev: 0 (0.0%) Runs: 1 1 1 1 1 1 1 1 1 1 Render issues:

Render Count Changes

There are no entries

Render Issues

There are no entries

Added Scenarios

There are no entries

Removed Scenarios

There are no entries

Generated by 🚫 dangerJS against 1835c5a