test: add liquidty cap field to sim tests for MsgWhitelistERC20

[kingpinXD]

Add liquidity cap field to sim tests for MsgWhitelistERC20

Summary by CodeRabbit

• New Features
  • Added a liquidity cap parameter for ERC20 whitelisting operations
  • Introduced support for configurable liquidity limits during cross-chain token whitelisting

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces a new LiquidityCap field to the MsgWhitelistERC20 struct in the crosschain simulation module. This modification involves adding an sdkmath.Uint type field initialized with a randomly generated unsigned integer between 1 and 1,000,000,000,000,000,000. The change extends the existing message structure for whitelisting ERC20 tokens during simulation, providing an additional parameter for liquidity management.

Changes

File	Change Summary
x/crosschain/simulation/operation_whitelist_erc20.go	Added sdkmath import and initialized LiquidityCap with random unsigned integer

Possibly related PRs

• test: initialize liquidity cap for newly deployed erc20 in WhiteListERC20 e2e test #2891: Initializes liquidity cap for ERC20 token in test function
• feat: add liquidity cap parameter to ZRC20 creation #3353: Introduces liquidityCap parameter for whitelisting and deployment messages
• test(e2e): fix add liquidity occasional error (tentative) #3199: Contains changes to liquidity-related methods

Suggested Labels

breaking:proto, ADMIN_TESTS

Suggested Reviewers

• lumtis
• skosito
• fbac
• brewmaster012

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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

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: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 115b21e and e59e8eb.

📒 Files selected for processing (1)

• x/crosschain/simulation/operation_whitelist_erc20.go (2 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

x/crosschain/simulation/operation_whitelist_erc20.go (1)

Pattern **/*.go: Review the Go code, point out issues relative to principles of clean code, expressiveness, and performance.

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

• GitHub Check: start-e2e-test / e2e

🔇 Additional comments (1)

x/crosschain/simulation/operation_whitelist_erc20.go (1)

6-6: LGTM: Import follows Cosmos SDK conventions.

The sdkmath import is correctly placed and properly aliased.