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

feat(native-app): update nav bar right buttons and title on all tab screens should be big #15478

Merged
merged 2 commits into from
Jul 11, 2024

Conversation

thoreyjona
Copy link
Contributor

@thoreyjona thoreyjona commented Jul 9, 2024

What

Updating nav bar buttons. Only show notification bell on home screen and settings icon on more screen. Move scan icon on wallet screen to be on the right side instead of left.

Why

Simplify nav bar buttons and create space for screen specific buttons when needed.

Screenshots / Gifs

Screen.Recording.2024-07-09.at.11.36.12.mov

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

  • New Features

    • Enhanced navigation bar with dynamic button sets based on the current screen.
  • Refactor

    • Updated button configuration logic to be screen-specific for Home, Wallet, and More screens.
  • Bug Fixes

    • Removed obsolete useActiveTabItemPress logic to improve performance and code maintainability.

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

coderabbitai bot commented Jul 9, 2024

Walkthrough

The recent changes involve refining the button functionality and screen-specific logic across multiple screens in the app. The getRightButtons function has been updated to dynamically generate buttons based on the current screen. Additionally, the useActiveTabItemPress hook has been removed from several components, leading to adjustments in the related logic.

Changes

Files Change Summary
...applications/applications.tsx Removed useActiveTabItemPress and getRightButtons imports and usage.
...home/home.tsx Updated rightButtons assignments to include screen-specific parameters in topBar and useConnectivityIndicator.
...inbox/inbox.tsx Removed getRightButtons import and usage in useNavigationOptions function.
...more/more.tsx Updated getRightButtons call to include parameters specifying the screen and theme.
...wallet/wallet.tsx Modified rightButtons property to include screen-specific parameters and removed useActiveTabItemPress.
...utils/get-main-root.ts Updated getRightButtons to return different button sets based on the screen parameter.

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: 1

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 482b75f and 3e867e8.

Files selected for processing (6)
  • apps/native/app/src/screens/applications/applications.tsx (4 hunks)
  • apps/native/app/src/screens/home/home.tsx (2 hunks)
  • apps/native/app/src/screens/inbox/inbox.tsx (3 hunks)
  • apps/native/app/src/screens/more/more.tsx (3 hunks)
  • apps/native/app/src/screens/wallet/wallet.tsx (2 hunks)
  • apps/native/app/src/utils/get-main-root.ts (1 hunks)
Files skipped from review due to trivial changes (1)
  • apps/native/app/src/screens/applications/applications.tsx
Additional context used
Path-based instructions (5)
apps/native/app/src/utils/get-main-root.ts (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/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/home/home.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."
Biome
apps/native/app/src/screens/inbox/inbox.tsx

[error] 50-50: Shouldn't redeclare 'ListItem'. Consider to delete it or rename it.

'ListItem' is defined here:

(lint/suspicious/noRedeclare)

Additional comments not posted (10)
apps/native/app/src/utils/get-main-root.ts (2)

13-19: Type definition for RightButtonProps looks good.

The addition of the optional screen property is correct and aligns with the function's usage.


20-68: getRightButtons function changes look good.

The function correctly handles different screens and returns appropriate button configurations. Ensure that this function is used correctly in all relevant components.

apps/native/app/src/screens/more/more.tsx (2)

37-39: Usage of getRightButtons in createNavigationOptionHooks looks good.

The screen parameter is correctly set to 'More', aligning with the updated function signature.


76-79: Usage of getRightButtons in useConnectivityIndicator looks good.

The screen parameter is correctly set to 'More', aligning with the updated function signature.

apps/native/app/src/screens/home/home.tsx (2)

51-53: Usage of getRightButtons in createNavigationOptionHooks looks good.

The screen parameter is correctly set to 'Home', aligning with the updated function signature.


115-117: Usage of getRightButtons in useConnectivityIndicator looks good.

The screen parameter is correctly set to 'Home', aligning with the updated function signature.

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

57-59: Usage of getRightButtons in createNavigationOptionHooks looks good.

The screen parameter is correctly set to 'Wallet', aligning with the updated function signature.


130-132: Usage of getRightButtons in useConnectivityIndicator looks good.

The screen parameter is correctly set to 'Wallet', aligning with the updated function signature.

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

Line range hint 1-1:
Verify the impact of removing getRightButtons.

Ensure that the removal of the getRightButtons function does not affect the functionality of the navigation bar. Confirm that alternative logic has been implemented to handle the right buttons.

Tools
Biome

[error] 50-50: Shouldn't redeclare 'ListItem'. Consider to delete it or rename it.

'ListItem' is defined here:

(lint/suspicious/noRedeclare)


Line range hint 1-1:
Verify the impact of removing useActiveTabItemPress.

Ensure that the removal of the useActiveTabItemPress hook does not affect the functionality of the tab navigation. Confirm that alternative logic has been implemented to handle tab item press events.

Tools
Biome

[error] 50-50: Shouldn't redeclare 'ListItem'. Consider to delete it or rename it.

'ListItem' is defined here:

(lint/suspicious/noRedeclare)

apps/native/app/src/screens/inbox/inbox.tsx Show resolved Hide resolved
@thoreyjona thoreyjona changed the title feat(native-app): update nav bar right buttons feat(native-app): update nav bar right buttons and title on all pages should be big Jul 9, 2024
@thoreyjona thoreyjona changed the title feat(native-app): update nav bar right buttons and title on all pages should be big feat(native-app): update nav bar right buttons and title on all tab screens should be big Jul 9, 2024
Copy link
Member

@eirikurn eirikurn left a comment

Choose a reason for hiding this comment

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

LGTM

@thoreyjona thoreyjona added the automerge Merge this PR as soon as all checks pass label Jul 10, 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 3e867e8 and d27b610.

Files selected for processing (3)
  • apps/native/app/src/screens/applications/applications.tsx (4 hunks)
  • apps/native/app/src/screens/more/more.tsx (3 hunks)
  • apps/native/app/src/utils/get-main-root.ts (1 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/utils/get-main-root.ts

@kodiakhq kodiakhq bot merged commit 90e51fa into main Jul 11, 2024
25 checks passed
@kodiakhq kodiakhq bot deleted the feat/update-app-nav-bar branch July 11, 2024 09:38
oskarjs pushed a commit that referenced this pull request Aug 20, 2024
…creens should be big (#15478)

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
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