Auto switch l2 network

[joshklop]

Summary by CodeRabbit

• New Features

  • Removed the Monomer L2 Wallet Integration section from the wallet application interface.
  • Introduced enhanced integration with the Keplr wallet, improving overall functionality.

• Bug Fixes

  • Improved error handling for user rejection during network addition requests, providing clearer error messages.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request modifies the wallet application's user interface and functionality. It removes the section related to the Monomer L2 Wallet Integration from index.html, focusing instead on the Metamask integration. Additionally, a new asynchronous function, runKeplrIntegration(), is introduced in metamask-integration.js, enhancing the integration with the Keplr wallet. Error handling in the addL1ChainToMetaMask() function is also improved to provide clearer feedback to users.

Changes

File Path	Change Summary
cmd/monogen/testapp/wallet/index.html	Removed <div class="container"> containing "Monomer L2 Wallet Integration" and related content.
cmd/monogen/testapp/wallet/metamask-integration.js	Added async function runKeplrIntegration(), modified error handling in addL1ChainToMetaMask().

Possibly related PRs

• Add keplr integration for L2 devnet chain #246: The changes in this PR involve the integration of the Keplr wallet, which is directly related to the modifications made in the main PR regarding the removal of the Monomer L2 Wallet Integration section, as both deal with wallet integrations.
• Automatically switch wallet network #275: This PR updates the wallet integration process, specifically for MetaMask, which is relevant to the main PR's changes that also involve wallet integration instructions and user interface elements.

Suggested reviewers

• natebeauregard

Poem

In the wallet’s bright space,
Monomer L2 has no place.
Keplr joins the fun,
With Metamask, we run!
Let’s hop through the code,
On this integration road! 🐰✨

---

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

[natebeauregard]

@joshklop While testing custom prefixes for #273 I realized that we'll probably want the step to add the L2 chain config to still be a button rather than having it immediately add on page load. If a user is using a custom prefix then the bech32Config that's passed to keplr will need to be updated with the expected bech32 prefixes.

We'll probably need the user to add their prefix through a text input field and then we can update the bech32 config for them whenever they click the button to add their chain to Keplr.

[natebeauregard]

@joshklop While testing custom prefixes for #273 I realized that we'll probably want the step to add the L2 chain config to still be a button rather than having it immediately add on page load. If a user is using a custom prefix then the bech32Config that's passed to keplr will need to be updated with the expected bech32 prefixes.

We'll probably need the user to add their prefix through a text input field and then we can update the bech32 config for them whenever they click the button to add their chain to Keplr.

For visibility - Talked about this in the daily meeting and we won't include the custom prefix change in this PR. That work will be included in #282