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: simplify epoch hooks #21552

Merged
merged 1 commit into from
Sep 5, 2024
Merged

refactor: simplify epoch hooks #21552

merged 1 commit into from
Sep 5, 2024

Conversation

julienrbrt
Copy link
Member

@julienrbrt julienrbrt commented Sep 4, 2024

Description

Don't know why this was there in the first place. The invoker creates multi hooks based on the depinject keys


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • New Features

    • Streamlined the EpochHooks interface by removing the GetModuleName method, simplifying implementation requirements.
  • Bug Fixes

    • Adjusted the dummyEpochHook struct to remove the GetModuleName method, reflecting updated handling of module names.
  • Chores

    • Updated the go.mod file to redirect the epochs module to a local path for development and testing purposes.

Copy link
Contributor

coderabbitai bot commented Sep 4, 2024

Walkthrough

Walkthrough

The changes involve the removal of the GetModuleName method from the EpochHooks interface and its implementations in the MultiEpochHooks and AppModule types. Additionally, the dummyEpochHook struct in the test file has also had this method removed. Furthermore, a new replacement directive has been added to the go.mod file to redirect the module path for epochs to a local implementation.

Changes

Files Change Summary
x/epochs/types/hooks.go, x/epochs/types/hooks_test.go, x/mint/epoch_hooks.go Removed GetModuleName method from EpochHooks interface and its implementations, including dummyEpochHook and AppModule.
x/mint/go.mod Added a replacement directive to redirect cosmossdk.io/x/epochs to a local path ../epochs.

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

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.

@julienrbrt julienrbrt added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Sep 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: 0

Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7f1eeb1 and a074928.

Files ignored due to path filters (1)
  • x/mint/go.sum is excluded by !**/*.sum
Files selected for processing (4)
  • x/epochs/types/hooks.go (1 hunks)
  • x/epochs/types/hooks_test.go (1 hunks)
  • x/mint/epoch_hooks.go (1 hunks)
  • x/mint/go.mod (1 hunks)
Files skipped from review due to trivial changes (2)
  • x/epochs/types/hooks_test.go
  • x/mint/epoch_hooks.go
Additional context used
Path-based instructions (1)
x/epochs/types/hooks.go (1)

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

Additional comments not posted (4)
x/epochs/types/hooks.go (3)

Line range hint 15-39: LGTM!

The removal of the GetModuleName method from the MultiEpochHooks type aligns with the removal of the method from the EpochHooks interface.


Line range hint 1-48: Code style looks good!

The Go code in this file follows the Uber Go Style Guide. There are no deviations from the style guide.


Line range hint 7-11: Verify the impact of removing the GetModuleName method from the EpochHooks interface.

The removal of the GetModuleName method from the EpochHooks interface simplifies the interface for implementers. However, it may break existing implementations of the interface.

Please run the following script to verify that all implementations of the EpochHooks interface have been updated to remove the GetModuleName method:

The first command searches for structs that embed the EpochHooks interface. The second command searches for implementations of the GetModuleName method. If the second command returns any results, it indicates that some implementations of the EpochHooks interface still have the GetModuleName method and need to be updated.

Verification successful

No Impact from Removal of GetModuleName Method from EpochHooks Interface

The removal of the GetModuleName method from the EpochHooks interface does not impact the current codebase, as no direct implementations of this interface were found. The instances of GetModuleName found in the codebase are unrelated to the EpochHooks interface.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash

# Search for implementations of the EpochHooks interface
ast-grep --lang go --pattern $'type $_ struct {
  $$$
  EpochHooks
  $$$
}'

# Search for implementations of the GetModuleName method
ast-grep --lang go --pattern $'func ($_ $_) GetModuleName() string {
  $$$
}'

Length of output: 2325

x/mint/go.mod (1)

188-188: LGTM!

The new replacement directive for the epochs module looks good. It is consistent with the existing replacements and does not introduce any issues.

@julienrbrt julienrbrt added this pull request to the merge queue Sep 5, 2024
Merged via the queue into main with commit 30688b0 Sep 5, 2024
77 of 78 checks passed
@julienrbrt julienrbrt deleted the julien/epochs branch September 5, 2024 09:46
mergify bot pushed a commit that referenced this pull request Sep 5, 2024
(cherry picked from commit 30688b0)

# Conflicts:
#	x/mint/go.sum
julienrbrt added a commit that referenced this pull request Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release C:x/epochs C:x/mint
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants