Skip to content

Comments

minor fixes on history update userOp status#364

Merged
RanaBug merged 1 commit intostagingfrom
fix/history-userop-status-update
Jul 7, 2025
Merged

minor fixes on history update userOp status#364
RanaBug merged 1 commit intostagingfrom
fix/history-userop-status-update

Conversation

@RanaBug
Copy link
Collaborator

@RanaBug RanaBug commented Jul 7, 2025

Description

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Summary by CodeRabbit

  • Bug Fixes
    • Adjusted the display logic for transaction status and related buttons, ensuring that chain ID '137' is handled distinctly for both confirmed and failed transactions.
    • Simplified the prompt for checking transaction status on a blockchain explorer for improved clarity.

@RanaBug RanaBug requested a review from IAmKio July 7, 2025 13:43
@RanaBug RanaBug self-assigned this Jul 7, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 7, 2025

Walkthrough

The changes update the TransactionInfo component's rendering logic to adjust how transaction status and related buttons are displayed. Special handling is introduced for chain ID '137' and failed transactions, modifying which buttons appear and the parameters used in blockchain explorer URLs. No exported or public entity signatures are altered.

Changes

File(s) Change Summary
src/components/BottomMenuModal/HistoryModal/TransactionInfo.tsx Refactored conditional rendering for transaction status and "View transaction" button; added special logic for chain ID '137' and failed transactions; simplified UI structure.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant TransactionInfo Component
    participant Blockchain Explorer

    User->>TransactionInfo Component: View transaction details
    alt displayStatus == 'Confirmed' and displayChainId != '137'
        TransactionInfo Component->>User: Show "View transaction" button (uses tx hash)
        User->>Blockchain Explorer: Opens transaction URL with hash
    else displayStatus == 'Failed' or displayChainId == '137'
        TransactionInfo Component->>User: Show "View transaction" button (uses wallet address, failed param)
        User->>Blockchain Explorer: Opens explorer URL with wallet address and failed status
    end
Loading

Possibly related PRs

Suggested reviewers

  • IAmKio
  • vignesha22

Poem

A button here, a status there,
Chain 137 gets special care.
Transactions failed or simply done,
The explorer waits for everyone.
With logic tweaked, the code is neat—
A rabbit’s hop makes UI sweet! 🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

npm error Exit handler never called!
npm error This is an error with npm itself. Please report this error at:
npm error https://github.com/npm/cli/issues
npm error A complete log of this run can be found in: /.npm/_logs/2025-07-07T13_44_08_372Z-debug-0.log

✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

@cloudflare-workers-and-pages
Copy link

Deploying x with  Cloudflare Pages  Cloudflare Pages

Latest commit: 73b1673
Status: ✅  Deploy successful!
Preview URL: https://9ae15fd0.x-e62.pages.dev
Branch Preview URL: https://fix-history-userop-status-up.x-e62.pages.dev

View logs

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 UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b246555 and 73b1673.

📒 Files selected for processing (1)
  • src/components/BottomMenuModal/HistoryModal/TransactionInfo.tsx (2 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: RanaBug
PR: pillarwallet/x#320
File: src/components/BottomMenuModal/HistoryModal/TransactionInfo.tsx:177-182
Timestamp: 2025-05-28T14:30:02.702Z
Learning: In the transaction history tracking feature, chain ID validation is performed earlier in the flow before the values reach the TransactionInfo component, so additional validation at the display level is not needed.
src/components/BottomMenuModal/HistoryModal/TransactionInfo.tsx (1)
Learnt from: RanaBug
PR: pillarwallet/x#320
File: src/components/BottomMenuModal/HistoryModal/TransactionInfo.tsx:177-182
Timestamp: 2025-05-28T14:30:02.702Z
Learning: In the transaction history tracking feature, chain ID validation is performed earlier in the flow before the values reach the TransactionInfo component, so additional validation at the display level is not needed.
🧬 Code Graph Analysis (1)
src/components/BottomMenuModal/HistoryModal/TransactionInfo.tsx (1)
src/utils/blockchain.ts (2)
  • getBlockScanName (239-258)
  • getBlockScan (218-237)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: unit-tests
  • GitHub Check: lint
  • GitHub Check: build
🔇 Additional comments (2)
src/components/BottomMenuModal/HistoryModal/TransactionInfo.tsx (2)

231-253: Clarify the combined condition logic for failed transactions and Polygon handling.

The condition (displayStatus === 'Failed' || displayChainId === '137') combines two different scenarios:

  1. Failed transactions (any chain) → show wallet address
  2. Polygon transactions (any status) → show wallet address

This creates inconsistent behavior where Polygon transactions are always directed to the wallet address view, regardless of success/failure status.

Please clarify if this is the intended behavior. The current logic means:

  • Failed transactions on any chain: wallet address view
  • Any transaction on Polygon: wallet address view
  • Successful transactions on non-Polygon: transaction hash view

Consider separating these conditions if they serve different purposes:

-        {(displayStatus === 'Failed' || displayChainId === '137') &&
-          displayChainId && (
+        {displayStatus === 'Failed' && displayChainId && (
+          <button>...</button>
+        )}
+        {displayChainId === '137' && displayChainId && (
           <button>...</button>
         )}

207-229: Confirm Polygon exclusion from “View transaction”
The displayChainId !== '137' check in TransactionInfo.tsx prevents the “View transaction” button from rendering on confirmed Polygon (chain 137) transactions. Please verify the business rationale (for example, Polygonscan’s current lack of support for EIP-4337 userOps) and confirm whether this special-case guard is still required or can be removed.

• File: src/components/BottomMenuModal/HistoryModal/TransactionInfo.tsx (lines 207–229)

Comment on lines +170 to +173
<p className="text-xs white font-normal">
Please check the transaction status on{' '}
{getBlockScanName(Number(displayChainId))}:
</p>
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix CSS class name for proper Tailwind styling.

The CSS class white should be text-white for consistency with Tailwind CSS naming conventions.

-                <p className="text-xs white font-normal">
+                <p className="text-xs text-white font-normal">
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<p className="text-xs white font-normal">
Please check the transaction status on{' '}
{getBlockScanName(Number(displayChainId))}:
</p>
<p className="text-xs text-white font-normal">
Please check the transaction status on{' '}
{getBlockScanName(Number(displayChainId))}:
</p>
🤖 Prompt for AI Agents
In src/components/BottomMenuModal/HistoryModal/TransactionInfo.tsx around lines
170 to 173, the CSS class name "white" is incorrect for Tailwind CSS and should
be changed to "text-white" to apply the proper text color styling.

Copy link
Collaborator

@IAmKio IAmKio left a comment

Choose a reason for hiding this comment

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

LGTM

@RanaBug RanaBug merged commit 7f0badf into staging Jul 7, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants