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

refactor: Remove the use of sdk LegacyMsg #93

Merged
merged 7 commits into from
Mar 11, 2024
Merged

Conversation

JulianToledano
Copy link
Contributor

@JulianToledano JulianToledano commented Mar 5, 2024

Closes:
#98

This PR replaces the use of sdk.LegacyMsg.GetSigners() in favor of codec.GetMsgV1Signers.

Copy link

coderabbitai bot commented Mar 5, 2024

Walkthrough

The recent updates introduce a new plugin-debug target for building a debug version of the Cosmos Hub plugin, alongside modifications in converter.go that streamline import usage, error handling, and the way signers and rosettatypes.Operation instances are managed. Additionally, a previously commented test in converter_test.go has been re-enabled, ensuring the successful conversion of Rosetta operations to transactions is properly verified. These changes aim to enhance debugging capabilities and improve the codebase's efficiency and readability.

Changes

File(s) Summary
Makefile, plugins/cosmos-hub/makefile Added a plugin-debug target to build the Cosmos Hub plugin with debug flags.
converter.go Updated imports, error handling, signers retrieval, and rosettatypes.Operation construction.
converter_test.go Uncommented TestFromRosettaOpsToTxSuccess to restore test logic for successful conversion.

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:

Note: Auto-reply has been disabled for this repository by the repository owner. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • 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 tests 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 tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Copy link

github-actions bot commented Mar 5, 2024

@JulianToledano your pull request is missing a changelog!

@JulianToledano JulianToledano changed the title Remove the use of sdk LegacyMsg refactor: Remove the use of sdk LegacyMsg Mar 5, 2024
converter.go Outdated Show resolved Hide resolved
converter.go Outdated Show resolved Hide resolved
CHANGELOG.md Show resolved Hide resolved
converter.go Outdated Show resolved Hide resolved
converter.go Outdated Show resolved Hide resolved
converter.go Outdated
for i, signer := range legacyMsg.GetSigners() {
ops := make([]*rosettatypes.Operation, len(signers))
for i, signer := range signers {
addr, _ := c.cdc.InterfaceRegistry().SigningContext().AddressCodec().BytesToString(signer)
Copy link
Contributor

Choose a reason for hiding this comment

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

is there a risk of encountering a nil pointer dereference at any point in this sequence?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It should not, the codec already uses that internally, although we could make a check when initialising rosetta to make sure SigningContext is correctly set.

@JulianToledano JulianToledano linked an issue Mar 7, 2024 that may be closed by this pull request
@JulianToledano JulianToledano merged commit f253ec2 into main Mar 11, 2024
13 checks passed
@JulianToledano JulianToledano deleted the feat/tests branch March 11, 2024 16:45
@coderabbitai coderabbitai bot mentioned this pull request Mar 11, 2024
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.

[Bug]: /block request ends with error
3 participants