fix style

[xixixueling]

Summary by CodeRabbit

• New Features

  • Expanded wallet connection support with added integrations across various platforms.
  • Updated connection button display now shows “OneKey Hardware & Phantom,” making hardware wallet selection clearer.

• Refactor

  • Streamlined the wallet connection process by consolidating provider support for a cleaner, more focused experience.

[coderabbitai]

Walkthrough

This update removes support for three wallet providers from the connect button hack functionality. The code now omits the integrations for lidofi, rocketpool, and solv by deleting their import statements, function calls, and dedicated files. Additionally, the configuration file has been updated to remove an unused ledger text update and to add several new site configurations. These changes streamline the connect button logic by focusing on the remaining providers and expanding support for new wallet connection setups.

Changes

File(s)	Change Summary
packages/providers/inpage-providers-hub/src/connectButtonHack/index.ts	Removed import statements and function calls for lidofi, rocketpool, and solv from the hackAllConnectButtons function.
packages/providers/inpage-providers-hub/src/connectButtonHack/sites/lidofi.ts, .../rocketpool.ts, .../solv.ts	Deleted the provider-specific files that customized wallet connection buttons.
packages/providers/inpage-providers-hub/src/connectButtonHack/universal/config.ts	Removed an outdated ledger text update and added new configuration entries for several URLs with corresponding wallet provider details.

Sequence Diagram(s)

sequenceDiagram
    participant Browser as User Browser
    participant CBH as ConnectButtonHack
    participant Config as SitesConfig

    Browser->>CBH: Invoke connect button update
    CBH->>Config: Retrieve site configuration
    Config-->>CBH: Return providers (excludes lidofi, rocketpool, solv)
    CBH->>Browser: Update wallet buttons for remaining providers

Loading

sequenceDiagram
    participant UI as Wallet Modal UI
    participant Config as SitesConfig

    UI->>Config: Request configuration
    Config-->>UI: Return new configuration entries
    UI->>UI: Update text node ("OneKey Hardware & Phantom")

Loading

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4b2fffe and 193098e.

📒 Files selected for processing (5)

• packages/providers/inpage-providers-hub/src/connectButtonHack/index.ts (0 hunks)
• packages/providers/inpage-providers-hub/src/connectButtonHack/sites/lidofi.ts (0 hunks)
• packages/providers/inpage-providers-hub/src/connectButtonHack/sites/rocketpool.ts (0 hunks)
• packages/providers/inpage-providers-hub/src/connectButtonHack/sites/solv.ts (0 hunks)
• packages/providers/inpage-providers-hub/src/connectButtonHack/universal/config.ts (2 hunks)

💤 Files with no reviewable changes (4)

• packages/providers/inpage-providers-hub/src/connectButtonHack/index.ts
• packages/providers/inpage-providers-hub/src/connectButtonHack/sites/rocketpool.ts
• packages/providers/inpage-providers-hub/src/connectButtonHack/sites/solv.ts
• packages/providers/inpage-providers-hub/src/connectButtonHack/sites/lidofi.ts

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

• GitHub Check: lint (ubuntu-latest, 20)
• GitHub Check: test_build_web

🔇 Additional comments (2)

packages/providers/inpage-providers-hub/src/connectButtonHack/universal/config.ts (2)

316-332: Clear user-facing improvement to wallet selection UI

The changes improve how OneKey Hardware & Phantom wallets are presented to users, making the connection options clearer and better styled.

---

4360-4679:

✅ Verification successful

Good addition of wallet provider configurations

The PR adds support for multiple new sites with proper wallet integration configurations. Each implementation follows existing patterns and handles site-specific requirements appropriately.

Note: There appears to be duplicate entries for 'desyn.io' (one at line 4338 and another at line 4463). This might be intentional if they serve different purposes, but worth confirming.

---

🏁 Script executed:

#!/bin/bash
# Check for duplicate entries and their differences
echo "Checking for duplicate URL configurations:"
grep -n "urls: \['desyn.io'" packages/providers/inpage-providers-hub/src/connectButtonHack/universal/config.ts

Length of output: 242

---

Wallet Provider Configurations Approved

The PR adds solid support for several new sites with wallet integrations. All configurations follow established patterns and handle site-specific needs well. The earlier note on duplicate 'desyn.io' entries appears to be a mistake—only one configuration is present (line 4463).

✨ 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

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