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

chore: move logic for getting packet data to its own function #6475

Merged
merged 4 commits into from
Jun 5, 2024

Conversation

DimitrisJim
Copy link
Contributor

@DimitrisJim DimitrisJim commented Jun 4, 2024

Description

closes: #6468


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against the correct branch (see CONTRIBUTING.md).
  • Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
  • Code follows the module structure standards and Go style guide.
  • Wrote unit and integration tests.
  • Updated relevant documentation (docs/).
  • Added relevant godoc comments.
  • Provide a conventional commit message to follow the repository standards.
  • Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
  • Re-reviewed Files changed in the GitHub PR explorer.
  • Review SonarCloud Report in the comment section below once CI passes.

Summary by CodeRabbit

  • Refactor

    • Simplified the sendTransfer function by consolidating packet data creation into a new function.
  • Tests

    • Added new test cases to validate packet data creation based on different application versions.

Copy link
Contributor

coderabbitai bot commented Jun 4, 2024

Warning

Rate limit exceeded

@DimitrisJim has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 15 minutes and 47 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 49dbd9a and 139e70d.

Walkthrough

The recent changes in the modules/apps/transfer/keeper module focus on refactoring and testing the creation of packet data bytes based on the application version. The core logic for creating these bytes has been moved to a new function, createPacketDataBytesFromVersion, simplifying the existing sendTransfer function. Additionally, new tests have been introduced to ensure the functionality works as expected.

Changes

Files/Modules Change Summary
modules/apps/transfer/keeper/export_test.go Added a test wrapper function CreatePacketDataBytesFromVersion for createPacketDataBytesFromVersion.
modules/apps/transfer/keeper/relay.go Refactored to include a new function createPacketDataBytesFromVersion to handle packet data creation logic.
modules/apps/transfer/keeper/relay_test.go Added new test cases for createPacketDataBytesFromVersion and imported the ibcmock package for testing.

Sequence Diagram(s) (Beta)

sequenceDiagram
    participant sendTransfer
    participant createPacketDataBytesFromVersion
    participant PacketData

    sendTransfer ->> createPacketDataBytesFromVersion: Request to create packet data bytes
    createPacketDataBytesFromVersion ->> PacketData: Create packet data based on app version
    PacketData -->> createPacketDataBytesFromVersion: Return packet data bytes
    createPacketDataBytesFromVersion -->> sendTransfer: Return packet data bytes
Loading

Assessment against linked issues

Objective Addressed Explanation
Move logic for creating packet data bytes to own function (#6468)
Test the new packet data creation function (#6468)

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

Comment on lines +450 to +453
// Sanity check, tokens must always be of length 1 if using app version V1.
if len(tokens) != 1 {
panic(fmt.Errorf("length of tokens must be equal to 1 if using %s version", types.V1))
}
Copy link
Contributor Author

@DimitrisJim DimitrisJim Jun 4, 2024

Choose a reason for hiding this comment

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

not seeing this used elsewhere but since it has been moved to func that might be re-used I added the explicit check to avoid the nasty panic if empty/faulty logic if > 1.

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

Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7598976 and 8eee9a0.

Files selected for processing (3)
  • modules/apps/transfer/keeper/export_test.go (1 hunks)
  • modules/apps/transfer/keeper/relay.go (2 hunks)
  • modules/apps/transfer/keeper/relay_test.go (2 hunks)
Additional context used
Path-based instructions (3)
modules/apps/transfer/keeper/export_test.go (2)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.


Pattern **/*_test.go: "Assess the unit test code assessing sufficient code coverage for the changes associated in the pull request"

modules/apps/transfer/keeper/relay.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

modules/apps/transfer/keeper/relay_test.go (2)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.


Pattern **/*_test.go: "Assess the unit test code assessing sufficient code coverage for the changes associated in the pull request"

golangci-lint
modules/apps/transfer/keeper/relay.go

55-55: undefined: Keeper (typecheck)


174-174: undefined: Keeper (typecheck)


314-314: undefined: Keeper (typecheck)


329-329: undefined: Keeper (typecheck)


337-337: undefined: Keeper (typecheck)


381-381: undefined: Keeper (typecheck)


397-397: undefined: Keeper (typecheck)


415-415: undefined: Keeper (typecheck)

Additional comments not posted (6)
modules/apps/transfer/keeper/export_test.go (1)

35-38: Add a comment explaining the purpose of this wrapper function.

+ // CreatePacketDataBytesFromVersion wraps the createPacketDataBytesFromVersion function to expose it for testing.
  func CreatePacketDataBytesFromVersion(appVersion, sender, receiver, memo string, tokens types.Tokens) []byte {
      return createPacketDataBytesFromVersion(appVersion, sender, receiver, memo, tokens)
  }

Likely invalid or redundant comment.

modules/apps/transfer/keeper/relay.go (1)

140-140: Centralization of packet data creation logic in sendTransfer enhances maintainability and clarity.

modules/apps/transfer/keeper/relay_test.go (4)

21-21: The import ibcmock "github.com/cosmos/ibc-go/v8/testing/mock" is correctly added and used in the test cases.


1249-1306: The setup for the test function TestCreatePacketDataBytesFromVersion is well-structured and clear, providing a good foundation for the test cases.


1255-1297: The test cases within TestCreatePacketDataBytesFromVersion are comprehensive, covering various scenarios including success and failure cases based on the app version.


1300-1318: The execution of test cases in TestCreatePacketDataBytesFromVersion is correctly implemented, effectively handling both expected results and error scenarios.


token := tokens[0]
packetData := types.NewFungibleTokenPacketData(token.Denom.Path(), token.Amount, sender, receiver, memo)
packetDataBytes = packetData.GetBytes()
Copy link
Contributor

Choose a reason for hiding this comment

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

could maybe just return early?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

no strong opinion either way, can def do if others would prefer.

@colin-axner colin-axner added the priority PRs that need prompt reviews label Jun 4, 2024
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: 1

Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8eee9a0 and 49dbd9a.

Files selected for processing (1)
  • modules/apps/transfer/keeper/relay.go (2 hunks)
Additional context used
Path-based instructions (1)
modules/apps/transfer/keeper/relay.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

golangci-lint
modules/apps/transfer/keeper/relay.go

55-55: undefined: Keeper (typecheck)


174-174: undefined: Keeper (typecheck)


314-314: undefined: Keeper (typecheck)


329-329: undefined: Keeper (typecheck)


337-337: undefined: Keeper (typecheck)


381-381: undefined: Keeper (typecheck)


397-397: undefined: Keeper (typecheck)


415-415: undefined: Keeper (typecheck)

Additional comments not posted (1)
modules/apps/transfer/keeper/relay.go (1)

445-466: Ensure the new function createPacketDataBytesFromVersion is adequately tested.

Verification successful

The test function TestCreatePacketDataBytesFromVersion is present and covers various scenarios, including success cases for both versions, as well as failure cases for invalid token length and invalid version. This indicates that the function createPacketDataBytesFromVersion is adequately tested.

  • modules/apps/transfer/keeper/relay_test.go:
    • Line 1249: func (suite *KeeperTestSuite) TestCreatePacketDataBytesFromVersion() {
    • Line 1262-1271: Success case for version V1.
    • Line 1272-1281: Success case for version V2.
    • Line 1282-1290: Failure case for invalid token length in version V1.
    • Line 1291-1297: Failure case for invalid version.
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the existence and adequacy of the test function for `createPacketDataBytesFromVersion`.

# Test: Search for the test function. Expect: At least one occurrence of the test function.
rg --type go $'TestCreatePacketDataBytesFromVersion'

Length of output: 165



Script:

#!/bin/bash
# Description: Extract the content of the test function `TestCreatePacketDataBytesFromVersion` to verify its adequacy.

# Extract the content of the test function.
ast-grep --lang go --pattern $'func (suite *KeeperTestSuite) TestCreatePacketDataBytesFromVersion() {
  $$$
}' modules/apps/transfer/keeper/relay_test.go

Length of output: 5100

Comment on lines +445 to +466
// createPacketDataBytesFromVersion creates the packet data bytes to be sent based on the application version.
func createPacketDataBytesFromVersion(appVersion, sender, receiver, memo string, tokens types.Tokens) []byte {
var packetDataBytes []byte
switch appVersion {
case types.V1:
// Sanity check, tokens must always be of length 1 if using app version V1.
if len(tokens) != 1 {
panic(fmt.Errorf("length of tokens must be equal to 1 if using %s version", types.V1))
}

token := tokens[0]
packetData := types.NewFungibleTokenPacketData(token.Denom.Path(), token.Amount, sender, receiver, memo)
packetDataBytes = packetData.GetBytes()
case types.V2:
packetData := types.NewFungibleTokenPacketDataV2(tokens, sender, receiver, memo)
packetDataBytes = packetData.GetBytes()
default:
panic(fmt.Errorf("app version must be one of %s", types.SupportedVersions))
}

return packetDataBytes
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Replace panic with error handling to improve robustness.

- panic(fmt.Errorf("length of tokens must be equal to 1 if using %s version", types.V1))
+ return nil, fmt.Errorf("length of tokens must be equal to 1 if using %s version", types.V1)
- panic(fmt.Errorf("app version must be one of %s", types.SupportedVersions))
+ return nil, fmt.Errorf("app version must be one of %s", types.SupportedVersions)

Committable suggestion was skipped due to low confidence.

Copy link
Contributor

@crodriguezvega crodriguezvega left a comment

Choose a reason for hiding this comment

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

Looks great to me!

Copy link

sonarqubecloud bot commented Jun 5, 2024

Quality Gate Passed Quality Gate passed for 'ibc-go'

Issues
12 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@DimitrisJim DimitrisJim merged commit fc6867e into main Jun 5, 2024
74 of 75 checks passed
@DimitrisJim DimitrisJim deleted the jim/move-packet-data-handling-to-func branch June 5, 2024 08:45
@DimitrisJim DimitrisJim mentioned this pull request Jun 5, 2024
16 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority PRs that need prompt reviews
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Move logic for creating packet data bytes to own function
3 participants