Skip to content

fix: argent mobile bug #1055

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

Merged
merged 1 commit into from
Feb 12, 2025
Merged

fix: argent mobile bug #1055

merged 1 commit into from
Feb 12, 2025

Conversation

Marchand-Nicolas
Copy link
Collaborator

@Marchand-Nicolas Marchand-Nicolas commented Feb 12, 2025

Summary by CodeRabbit

  • Bug Fixes

    • Enhanced wallet connection reliability with improved error handling and controlled retry logic.
  • Style

    • Refined the navigation UI for enhanced clarity and consistency.
  • Chores

    • Updated a dependency version to ensure consistent performance and stability.

@Marchand-Nicolas Marchand-Nicolas added the 🚧 In progress do not merge Pull Request in progress, please do not merge label Feb 12, 2025
Copy link

vercel bot commented Feb 12, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
app-starknet-id ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 12, 2025 5:11pm
sepolia-app-starknet-id ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 12, 2025 5:11pm

Copy link
Contributor

coderabbitai bot commented Feb 12, 2025

Walkthrough

The pull request modifies the wallet connection logic and JSX formatting in the Navbar component while adjusting a dependency version in the package configuration. The Navbar component now logs a more descriptive error on connection failure and delays its retry attempts by 200 milliseconds using setTimeout. Additionally, some JSX formatting improvements enhance code readability. In the package configuration, the starknetkit dependency version is changed from a caret specification to an exact version.

Changes

File(s) Change Summary
components/UI/navbar.tsx Enhanced error handling in connectWallet by replacing console.error(e) with console.error("Failed connecting", e) and introducing a 200ms retry delay via setTimeout. Reformatted JSX code for improved consistency and readability.
package.json Updated the starknetkit dependency from "^2.6.2" to "2.6.2", locking the version, and added a newline at the end of the file.

Sequence Diagram(s)

sequenceDiagram
    participant Navbar
    participant WalletService
    Navbar->>WalletService: Initiate wallet connection
    WalletService-->>Navbar: Return error on failure
    Navbar->>Navbar: Log "Failed connecting", error
    Navbar->>Navbar: Wait 200ms (setTimeout)
    Navbar->>WalletService: Retry connection
Loading

Suggested Labels

🔥 Ready for review

Suggested Reviewers

  • fricoben

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 647f80e and ea793fc.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (2)
  • components/UI/navbar.tsx (5 hunks)
  • package.json (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • package.json
  • components/UI/navbar.tsx

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>, 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. (Beta)
  • @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.

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

🧹 Nitpick comments (1)
components/UI/navbar.tsx (1)

171-179: Refactor duplicate StarkNet ID text component

The "StarkNet ID" text component is duplicated with identical styling logic. Consider extracting it into a reusable component to follow DRY principles.

Create a new component:

const StarkNetIdText: React.FC<{ isMobile: boolean }> = ({ isMobile }) => (
  <p
    className={`${
      styles.starknetId
    } text-[#454545] text-lg tracking-wide whitespace-nowrap text-nowrap leading-10 font-quickZap ${
      isMobile ? "hidden" : "block"
    }`}
  >
    StarkNet ID
  </p>
);

Then use it in both places:

-<p
-  className={`${
-    styles.starknetId
-  } text-[#454545] text-lg  tracking-wide whitespace-nowrap text-nowrap leading-10 font-quickZap ${
-    isMobile ? "hidden" : "block"
-  }`}
->
-  StarkNet ID
-</p>
+<StarkNetIdText isMobile={isMobile} />

Also applies to: 306-314

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between fad429f and 6ee5c20.

📒 Files selected for processing (1)
  • components/UI/navbar.tsx (5 hunks)
🔇 Additional comments (3)
components/UI/navbar.tsx (3)

95-95: LGTM! Improved error logging

The addition of a descriptive error message "Failed connecting" enhances debugging and error tracking capabilities.


168-169: Consider maintaining consistent aspect ratio

The current implementation has potential issues:

  1. Different aspect ratios between mobile (40x40) and desktop (40x90) could lead to image distortion
  2. The width remains constant while height changes, which is inconsistent

Consider either:

  1. Maintaining the same aspect ratio across devices
  2. Using CSS scaling instead of different dimensions
-width={isMobile ? 40 : 40}
-height={isMobile ? 40 : 90}
+width={40}
+height={40}
+className={`${styles.starknetIdLogo} ${!isMobile && 'scale-y-[2.25]'}`}

444-444: LGTM! Improved code formatting

The added newline before the export statement enhances code readability.

Copy link
Contributor

@fricoben fricoben left a comment

Choose a reason for hiding this comment

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

lgtm

@fricoben fricoben merged commit 5cee68a into testnet Feb 12, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔥 Ready for review This pull request needs a review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants