Skip to content
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

fix: ensure swapCoin functionality works correctly #942

Merged
merged 1 commit into from
Jan 22, 2025

Conversation

zakir-code
Copy link
Contributor

@zakir-code zakir-code commented Jan 22, 2025

Summary by CodeRabbit

  • Bug Fixes

    • Updated coin denomination handling to correctly swap legacy coin denominations to default denominations
    • Improved coin swapping logic to ensure accurate coin collection updates
  • Tests

    • Enhanced test cases to validate coin denomination swapping functionality
    • Added assertions to verify correct coin transformation

Copy link

coderabbitai bot commented Jan 22, 2025

Walkthrough

The pull request introduces modifications to coin denomination handling in the types/constant.go file. The changes primarily focus on updating the SwapCoin and SwapCoins functions to work with LegacyFXDenom instead of FXDenom. When a coin's denomination matches LegacyFXDenom, the function now sets the denomination to DefaultDenom while preserving the coin's amount. The accompanying test file constant_test.go has been updated to reflect these changes and add assertions to verify the new coin denomination behavior.

Changes

File Change Summary
types/constant.go - Updated SwapCoin to check against LegacyFXDenom instead of FXDenom
- Modified coin denomination setting logic in SwapCoin
- Changed coin addition method in SwapCoins
types/constant_test.go - Replaced FXDenom with LegacyFXDenom
- Added assertions to verify coin denomination swap

Possibly related PRs

Poem

🐰 Hopping through denominations with glee,
Swapping coins, setting them free!
Legacy FX, now DefaultDenom's might,
A rabbit's dance of coin delight! 🪙
Transformation complete, code so bright!

✨ 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
🪧 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

@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 (2)
types/constant_test.go (2)

55-58: Add test cases for complete coverage

While the current test verifies the happy path, we should add test cases for:

  1. Non-LegacyFXDenom coins (should remain unchanged)
  2. Edge cases like zero amount
  3. Verify the actual amount value, not just the string representation
 func TestSwapCoin(t *testing.T) {
 	coin := sdk.NewCoin(LegacyFXDenom, sdkmath.NewInt(100))
 	swapCoin := SwapCoin(coin)
 	assert.NotEqual(t, swapCoin.String(), coin.String())
 	assert.EqualValues(t, sdk.NewCoin(DefaultDenom, sdkmath.NewInt(1)).String(), swapCoin.String())
+
+	// Test non-LegacyFXDenom coin
+	otherCoin := sdk.NewCoin(DefaultDenom, sdkmath.NewInt(100))
+	swapOtherCoin := SwapCoin(otherCoin)
+	assert.Equal(t, otherCoin, swapOtherCoin)
+
+	// Test zero amount
+	zeroCoin := sdk.NewCoin(LegacyFXDenom, sdkmath.NewInt(0))
+	swapZeroCoin := SwapCoin(zeroCoin)
+	assert.Equal(t, DefaultDenom, swapZeroCoin.Denom)
+	assert.True(t, swapZeroCoin.Amount.IsZero())
 }

62-65: Add test cases for mixed denomination scenarios

The current test only verifies swapping a single LegacyFXDenom coin. We should add test cases for:

  1. Multiple coins with mixed denominations
  2. Empty coins collection
  3. Verify the actual amounts, not just the string representation
 func TestSwapCoins(t *testing.T) {
 	coins := sdk.NewCoins(sdk.NewCoin(LegacyFXDenom, sdkmath.NewInt(100)))
 	swapCoins := SwapCoins(coins)
 	assert.NotEqual(t, swapCoins.String(), coins.String())
 	assert.EqualValues(t, sdk.NewCoins(sdk.NewCoin(DefaultDenom, sdkmath.NewInt(1))).String(), swapCoins.String())
+
+	// Test mixed denominations
+	mixedCoins := sdk.NewCoins(
+		sdk.NewCoin(LegacyFXDenom, sdkmath.NewInt(100)),
+		sdk.NewCoin(DefaultDenom, sdkmath.NewInt(50)),
+	)
+	swapMixedCoins := SwapCoins(mixedCoins)
+	expected := sdk.NewCoins(
+		sdk.NewCoin(DefaultDenom, sdkmath.NewInt(1)),
+		sdk.NewCoin(DefaultDenom, sdkmath.NewInt(50)),
+	)
+	assert.Equal(t, expected, swapMixedCoins)
+
+	// Test empty coins
+	emptyCoins := sdk.NewCoins()
+	swapEmptyCoins := SwapCoins(emptyCoins)
+	assert.True(t, swapEmptyCoins.Empty())
 }
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c081999 and 9774d64.

📒 Files selected for processing (2)
  • types/constant.go (1 hunks)
  • types/constant_test.go (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Mergify Merge Protections
  • GitHub Check: Summary
🔇 Additional comments (2)
types/constant.go (2)

117-117: LGTM! Proper handling of Add result.

The change correctly captures the result of Add operation, fixing a potential bug where the result might have been lost.


106-110: Document the migration from FXDenom to LegacyFXDenom

The change from FXDenom to LegacyFXDenom suggests a migration path. This change needs to be documented to help users understand:

  1. Why we're switching to LegacyFXDenom
  2. The impact on existing coins
  3. Migration steps for users

Let's check for any remaining usages of FXDenom that might need updating:

@zakir-code zakir-code merged commit f25d103 into main Jan 22, 2025
13 checks passed
@zakir-code zakir-code deleted the fx0x55/swap-coin branch January 22, 2025 12:31
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