refactor: remove duplicate codes AFAP

[Nick-1979]

add useTransactionHistory hook

Summary by CodeRabbit

• New Features

  • Introduced a tabbed interface for viewing transaction history, allowing users to switch between ALL, TRANSFERS, and STAKING categories.
  • Added a custom hook to manage and retrieve transaction history efficiently, including pagination and dynamic loading of transactions.

• Bug Fixes

  • Streamlined the rendering logic and state management in various components to enhance performance and maintainability.

• Style

  • Improved the visual presentation and readability of the modal and history item components through minor styling adjustments.

• Refactor

  • Simplified the TransactionHistory and HistoryModal components, focusing on modularity and reducing complexity by utilizing hooks effectively.

[coderabbitai]

Walkthrough

The changes introduce a new HistoryTabs component that provides a tabbed interface for displaying transaction history categories. The TransactionHistory component has been refactored to simplify state management and utilize a new useTransactionHistory hook for data handling. The HistoryModal and HistoryItemModal components have been updated for better structure and maintainability. Additionally, various JSX formatting improvements and styling adjustments were made across several files to enhance readability and consistency.

Changes

Files	Change Summary
.../popup/history/HistoryTabs.tsx	Added HistoryTabs component with tabbed interface for history categories.
.../popup/history/index.tsx	Refactored TransactionHistory to use useTransactionHistory hook, removing complexity.
.../popup/history/modal/HistoryItemModal.tsx	Minor JSX structure and styling adjustments for improved readability.
.../popup/history/modal/HistoryModal.tsx	Refactored to simplify state management and incorporate HistoryTabs.
.../popup/history/partials/HistoryItem.tsx	Adjusted formatting and structure for better readability without changing functionality.
.../popup/history/useTransactionHistory.tsx	Introduced custom hook for managing transaction history, including fetching and pagination.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant HistoryTabs
    participant TransactionHistory
    participant useTransactionHistory

    User->>HistoryTabs: Selects a tab
    HistoryTabs->>TransactionHistory: Updates tabIndex
    TransactionHistory->>useTransactionHistory: Fetch transaction data
    useTransactionHistory-->>TransactionHistory: Returns transaction history
    TransactionHistory-->>User: Displays transaction data

Loading

🐰 In the meadow, hopping free,
A new component, oh what glee!
Tabs for history, neat and bright,
Fetching data, a pure delight.
With every click, the stories flow,
A joyful dance, let’s watch it grow! 🌼

Tip

New features

Walkthrough comment now includes:

• Possibly related PRs: A list of potentially related PRs to help you recall past context.
• Suggested labels: CodeRabbit can now suggest labels by learning from your past PRs. You can also provide custom labeling instructions in the UI or configuration file.

Notes:

• Please share any feedback in the discussion post on our Discord.
• Possibly related PRs, automatic label suggestions based on past PRs, learnings, and possibly related issues require data opt-in (enabled by default).

---

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>.
  • 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 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 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.

[coderabbitai]

Actionable comments posted: 2

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between dfe9156 and 4cfda2a.

Files selected for processing (6)

• packages/extension-polkagate/src/popup/history/HistoryTabs.tsx (1 hunks)
• packages/extension-polkagate/src/popup/history/index.tsx (2 hunks)
• packages/extension-polkagate/src/popup/history/modal/HistoryItemModal.tsx (2 hunks)
• packages/extension-polkagate/src/popup/history/modal/HistoryModal.tsx (4 hunks)
• packages/extension-polkagate/src/popup/history/partials/HistoryItem.tsx (5 hunks)
• packages/extension-polkagate/src/popup/history/useTransactionHistory.tsx (1 hunks)

Files skipped from review due to trivial changes (2)

• packages/extension-polkagate/src/popup/history/modal/HistoryItemModal.tsx
• packages/extension-polkagate/src/popup/history/partials/HistoryItem.tsx

Additional comments not posted (5)

packages/extension-polkagate/src/popup/history/index.tsx (3)

6-16: Import statements are correctly structured.

The import statements are well-organized, and the new useTransactionHistory hook is appropriately imported.

---

18-27: Proper use of React hooks for state management.

The component effectively uses React hooks (useState, useCallback) for state management, which aligns with modern React practices and enhances maintainability.

---

Line range hint 40-73: Well-structured rendering logic and JSX.

The component's rendering logic is clean and logically organized, effectively managing different states with conditional rendering. This enhances the user experience by providing clear feedback during data fetching and empty states.

packages/extension-polkagate/src/popup/history/HistoryTabs.tsx (1)

12-83: Well-implemented HistoryTabs component.

The HistoryTabs component is well-structured and effectively manages tab selection using React hooks and the TAB_MAP enum. The conditional rendering based on chain type is a good practice, ensuring that the UI adapts to different contexts.

packages/extension-polkagate/src/popup/history/modal/HistoryModal.tsx (1)

Line range hint 25-88: Proper use of React hooks and structured component logic in HistoryModal.

The HistoryModal component effectively uses React hooks for state management and data fetching, which aligns with modern React practices. The structured component logic, including the use of a dedicated HistoryTabs component, enhances maintainability and readability.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4cfda2a and c48694c.

Files selected for processing (2)

• packages/extension-polkagate/src/popup/history/modal/HistoryItemModal.tsx (3 hunks)
• packages/extension-polkagate/src/popup/history/partials/HistoryItem.tsx (5 hunks)

Files skipped from review due to trivial changes (1)

• packages/extension-polkagate/src/popup/history/partials/HistoryItem.tsx

Files skipped from review as they are similar to previous changes (1)

• packages/extension-polkagate/src/popup/history/modal/HistoryItemModal.tsx