Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(native-app): large title on all tab screens now fixed #15504

Merged
merged 2 commits into from
Jul 11, 2024

Conversation

thoreyjona
Copy link
Contributor

@thoreyjona thoreyjona commented Jul 11, 2024

What

Make sure we always show large titles in the top bar of the tab screens.
There is a bug in react-native-navigation/react-native so we need to do a workaround to make sure the large title is shown, see here: wix/react-native-navigation#6717

Checklist:

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • Formatting passes locally with my changes
  • I have rebased against main before asking for a review

Summary by CodeRabbit

  • Bug Fixes

    • Resolved an issue with large titles not being visible on iOS with bottom tabs across multiple screens (Applications, Inbox, More, Wallet).
  • New Features

    • Improved platform-specific visibility handling for content on iOS.
  • Chores

    • Updated exports in the UI module to include inbox-card.

@thoreyjona thoreyjona requested a review from a team as a code owner July 11, 2024 11:36
Copy link
Contributor

coderabbitai bot commented Jul 11, 2024

Walkthrough

The changes introduce the use of useNavigationComponentDidAppear from 'react-native-navigation-hooks' and isIos from '../../utils/devices' across multiple screens to manage the visibility of content based on the iOS platform. This addresses a specific issue with large titles not being visible on iOS when using bottom tabs. Additionally, an export for 'inbox-card' is added in the UI module.

Changes

File Path Change Summary
apps/native/app/src/screens/applications/applications.tsx Introduced useNavigationComponentDidAppear and isIos to control content visibility based on platform.
apps/native/app/src/screens/inbox/inbox.tsx Updated visibility control in InboxScreen component using the isIos flag.
apps/native/app/src/screens/more/more.tsx Utilized useState, useNavigationComponentDidAppear, and isIos to manage visibility state in MoreScreen.
apps/native/app/src/screens/wallet/wallet.tsx Applied useNavigationComponentDidAppear and isIos in WalletScreen to handle visibility issues on iOS.
apps/native/app/src/ui/index.ts Added export of './lib/card/inbox-card' in the UI module.

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
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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2242ffc and 48a2155.

Files selected for processing (4)
  • apps/native/app/src/screens/applications/applications.tsx (4 hunks)
  • apps/native/app/src/screens/inbox/inbox.tsx (4 hunks)
  • apps/native/app/src/screens/more/more.tsx (4 hunks)
  • apps/native/app/src/screens/wallet/wallet.tsx (4 hunks)
Additional context used
Path-based instructions (4)
apps/native/app/src/screens/more/more.tsx (1)

Pattern apps/**/*: "Confirm that the code adheres to the following:

  • NextJS best practices, including file structure, API routes, and static generation methods.
  • Efficient state management and server-side rendering techniques.
  • Optimal use of TypeScript for component and utility type safety."
apps/native/app/src/screens/applications/applications.tsx (1)

Pattern apps/**/*: "Confirm that the code adheres to the following:

  • NextJS best practices, including file structure, API routes, and static generation methods.
  • Efficient state management and server-side rendering techniques.
  • Optimal use of TypeScript for component and utility type safety."
apps/native/app/src/screens/wallet/wallet.tsx (1)

Pattern apps/**/*: "Confirm that the code adheres to the following:

  • NextJS best practices, including file structure, API routes, and static generation methods.
  • Efficient state management and server-side rendering techniques.
  • Optimal use of TypeScript for component and utility type safety."
apps/native/app/src/screens/inbox/inbox.tsx (1)

Pattern apps/**/*: "Confirm that the code adheres to the following:

  • NextJS best practices, including file structure, API routes, and static generation methods.
  • Efficient state management and server-side rendering techniques.
  • Optimal use of TypeScript for component and utility type safety."
Additional comments not posted (15)
apps/native/app/src/screens/more/more.tsx (4)

80-80: Initialize hiddenContent state for iOS.

The state hiddenContent is initialized to handle content visibility on iOS devices.


89-91: Set hiddenContent state to false when component appears.

The useNavigationComponentDidAppear hook is used to set hiddenContent to false when the component appears, ensuring the content is visible on iOS devices.


93-96: Add condition to render content based on hiddenContent state.

The content is rendered only if hiddenContent is false, which addresses the iOS large title visibility issue.


26-27: Add missing import for isIos.

Ensure the isIos utility is correctly imported from ../../utils/devices.

+ import { isIos } from '../../utils/devices'

Likely invalid or redundant comment.

apps/native/app/src/screens/applications/applications.tsx (4)

83-83: Initialize hiddenContent state for iOS.

The state hiddenContent is initialized to handle content visibility on iOS devices.


105-107: Set hiddenContent state to false when component appears.

The useNavigationComponentDidAppear hook is used to set hiddenContent to false when the component appears, ensuring the content is visible on iOS devices.


159-162: Add condition to render content based on hiddenContent state.

The content is rendered only if hiddenContent is false, which addresses the iOS large title visibility issue.


28-29: Add missing imports for useNavigationComponentDidAppear and isIos.

Ensure the useNavigationComponentDidAppear hook and isIos utility are correctly imported.

+ import { useNavigationComponentDidAppear } from 'react-native-navigation-hooks'
+ import { isIos } from '../../utils/devices'

Likely invalid or redundant comment.

apps/native/app/src/screens/wallet/wallet.tsx (4)

100-100: Initialize hiddenContent state for iOS.

The state hiddenContent is initialized to handle content visibility on iOS devices.


199-201: Set hiddenContent state to false when component appears.

The useNavigationComponentDidAppear hook is used to set hiddenContent to false when the component appears, ensuring the content is visible on iOS devices.


267-270: Add condition to render content based on hiddenContent state.

The content is rendered only if hiddenContent is false, which addresses the iOS large title visibility issue.


37-37: Add missing import for useNavigationComponentDidAppear.

Ensure the useNavigationComponentDidAppear hook is correctly imported from react-native-navigation-hooks.

+ import { useNavigationComponentDidAppear } from 'react-native-navigation-hooks'

Likely invalid or redundant comment.

apps/native/app/src/screens/inbox/inbox.tsx (3)

277-277: Initialize hiddenContent state for iOS.

The state hiddenContent is initialized to handle content visibility on iOS devices.


394-394: Set hiddenContent state to false when component appears.

The useNavigationComponentDidAppear hook is used to set hiddenContent to false when the component appears, ensuring the content is visible on iOS devices.


425-426: Add condition to render content based on hiddenContent state.

The content is rendered only if hiddenContent is false, which addresses the iOS large title visibility issue.

apps/native/app/src/screens/more/more.tsx Show resolved Hide resolved
apps/native/app/src/screens/inbox/inbox.tsx Show resolved Hide resolved
Copy link

codecov bot commented Jul 11, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 37.03%. Comparing base (97f20ab) to head (48a2155).
Report is 2 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main   #15504      +/-   ##
==========================================
- Coverage   37.04%   37.03%   -0.02%     
==========================================
  Files        6557     6557              
  Lines      134059   134042      -17     
  Branches    38380    38374       -6     
==========================================
- Hits        49668    49645      -23     
- Misses      84391    84397       +6     
Flag Coverage Δ
judicial-system-api 18.21% <ø> (+0.03%) ⬆️
judicial-system-backend 55.93% <ø> (-0.10%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 19 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 97f20ab...48a2155. Read the comment docs.

@datadog-island-is
Copy link

Datadog Report

All test runs 574c177 🔗

2 Total Test Services: 0 Failed, 2 Passed
➡️ Test Sessions change in coverage: 3 no change

Test Services
Service Name Failed Known Flaky New Flaky Passed Skipped Total Time Code Coverage Change Test Service View
judicial-system-api 0 0 0 54 0 6.15s 1 no change Link
judicial-system-backend 0 0 0 19911 0 19m 32.81s 1 no change Link

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 48a2155 and 15399f4.

Files selected for processing (3)
  • apps/native/app/src/screens/applications/applications.tsx (5 hunks)
  • apps/native/app/src/screens/more/more.tsx (5 hunks)
  • apps/native/app/src/screens/wallet/wallet.tsx (5 hunks)
Files skipped from review as they are similar to previous changes (3)
  • apps/native/app/src/screens/applications/applications.tsx
  • apps/native/app/src/screens/more/more.tsx
  • apps/native/app/src/screens/wallet/wallet.tsx

@thoreyjona thoreyjona force-pushed the fix/app-large-title-navigation branch from 15399f4 to c85f9c6 Compare July 11, 2024 12:43
@thoreyjona thoreyjona added the automerge Merge this PR as soon as all checks pass label Jul 11, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 15399f4 and c85f9c6.

Files selected for processing (5)
  • apps/native/app/src/screens/applications/applications.tsx (5 hunks)
  • apps/native/app/src/screens/inbox/inbox.tsx (5 hunks)
  • apps/native/app/src/screens/more/more.tsx (5 hunks)
  • apps/native/app/src/screens/wallet/wallet.tsx (5 hunks)
  • apps/native/app/src/ui/index.ts (1 hunks)
Files skipped from review due to trivial changes (1)
  • apps/native/app/src/ui/index.ts
Files skipped from review as they are similar to previous changes (4)
  • apps/native/app/src/screens/applications/applications.tsx
  • apps/native/app/src/screens/inbox/inbox.tsx
  • apps/native/app/src/screens/more/more.tsx
  • apps/native/app/src/screens/wallet/wallet.tsx

@kodiakhq kodiakhq bot merged commit 745b0f2 into main Jul 11, 2024
34 checks passed
@kodiakhq kodiakhq bot deleted the fix/app-large-title-navigation branch July 11, 2024 12:47
oskarjs pushed a commit that referenced this pull request Aug 20, 2024
* fix: large title on all tab screens now fixed

* fix: order of imports
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Merge this PR as soon as all checks pass
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants