-
Notifications
You must be signed in to change notification settings - Fork 170
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(unification): rename KeeperBuilder to Builder #2471
Conversation
WalkthroughThe overall change across the codebase involves a significant renaming effort, transitioning from the use of Changes
Poem
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? TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Additionally, you can add CodeRabbit Configration File (
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2471 +/- ##
==========================================
- Coverage 75.38% 69.38% -6.01%
==========================================
Files 100 185 +85
Lines 8025 10909 +2884
==========================================
+ Hits 6050 7569 +1519
- Misses 1589 2712 +1123
- Partials 386 628 +242
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review Status
Actionable comments generated: 2
Configuration used: CodeRabbit UI
Files selected for processing (18)
- app/app.go (4 hunks)
- x/metoken/keeper/intest/keeper_test.go (1 hunks)
- x/metoken/keeper/intest/msg_server_test.go (4 hunks)
- x/metoken/keeper/keeper.go (1 hunks)
- x/metoken/keeper/unit_test.go (1 hunks)
- x/ugov/keeper/intest/keeper.go (1 hunks)
- x/ugov/keeper/keeper.go (1 hunks)
- x/uibc/module/module.go (1 hunks)
- x/uibc/quota/genesis.go (2 hunks)
- x/uibc/quota/grpc_query.go (1 hunks)
- x/uibc/quota/intest/suite_test.go (1 hunks)
- x/uibc/quota/keeper.go (2 hunks)
- x/uibc/quota/msg_server.go (1 hunks)
- x/uibc/quota/unit_test.go (1 hunks)
- x/uibc/uics20/ibc_module.go (1 hunks)
- x/uibc/uics20/ibc_module_test.go (1 hunks)
- x/uibc/uics20/ics4_wrapper.go (1 hunks)
- x/uibc/uics20/ics4_wrapper_test.go (1 hunks)
Additional comments: 28
x/ugov/keeper/intest/keeper.go (1)
- 23-23: The renaming from
NewKeeperBuilder
toNewBuilder
aligns with the PR's objective to unify naming conventions. Ensure that theNewBuilder
function is correctly implemented in thekeeper
package and that its usage here is consistent with its definition.x/ugov/keeper/keeper.go (1)
- 18-18: The introduction of the
NewBuilder
function and theBuilder
type aligns with the PR's objective to unify naming conventions. The implementation is correct and facilitates the construction of aKeeper
instance with the necessary dependencies.x/uibc/uics20/ics4_wrapper.go (2)
- 17-17: The change in the
ICS4
struct fromquota.KeeperBuilder
toquota.Builder
aligns with the PR's objective to unify naming conventions. Ensure that thequota.Builder
type is correctly implemented and that its usage here is consistent with its definition.- 20-20: The update to the
NewICS4
function signature to usequota.Builder
is correctly implemented and aligns with the PR's objective. Ensure that thequota.Builder
type is correctly defined.x/metoken/keeper/unit_test.go (1)
- 25-25: The renaming from
NewKeeperBuilder
toNewBuilder
in theinitSimpleKeeper
function aligns with the PR's objective to unify naming conventions. Ensure that theNewBuilder
function is correctly implemented and that its usage here is consistent with its definition.x/uibc/quota/unit_test.go (1)
- 28-28: The renaming from
NewKeeperBuilder
toNewBuilder
in theinitKeeper
function aligns with the PR's objective to unify naming conventions. Ensure that theNewBuilder
function is correctly implemented and that its usage here is consistent with its definition.x/uibc/quota/keeper.go (2)
- 16-17: The introduction of the
Builder
type and theNewBuilder
function aligns with the PR's objective to unify naming conventions. The implementation is correct and facilitates the construction of aKeeper
instance with the necessary dependencies.- 25-29: The
NewBuilder
function is correctly implemented and aligns with the PR's objective. Ensure that theBuilder
type is correctly defined and that its usage here is consistent with its definition.x/uibc/quota/msg_server.go (2)
- 14-14: Renaming
KeeperBuilder
toBuilder
in themsgServer
struct aligns with the PR's objective to standardize naming conventions across the codebase.- 18-18: The update in the
NewMsgServerImpl
function to acceptBuilder
instead ofKeeperBuilder
is consistent with the renaming effort. However, it's noted that this line was not covered by tests.x/uibc/quota/grpc_query.go (2)
- 14-14: Renaming
KeeperBuilder
toBuilder
in theQuerier
struct aligns with the PR's objective to standardize naming conventions across the codebase.- 17-18: The update in the
NewQuerier
function to acceptBuilder
instead ofKeeperBuilder
is consistent with the renaming effort. However, it's noted that these lines were not covered by tests.Verification successful
The verification process has revealed that while there may not be direct tests specifically named to test the
NewQuerier
function, the function is indeed used across various parts of the codebase, including in test setups. This indicates that theNewQuerier
function is likely covered indirectly by tests that utilize these setups, such as insuite_test.go
andgrpc_query_test.go
files. Therefore, the concern about the lack of test coverage for theNewQuerier
function following the renaming effort is addressed through its integration and usage in the system's overall testing framework.Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Verify if NewQuerier function is covered by tests after renaming rg --type go "NewQuerier" --files-with-matches | xargs rg "func Test.*NewQuerier"Length of output: 81
Script:
#!/bin/bash # Search for any test files that reference the NewQuerier function to check for indirect testing rg --type go "NewQuerier" --files-with-matches | xargs rg --type go "func Test" # Additionally, verify the usage of the NewQuerier function in the codebase to understand its testing context better rg --type go "NewQuerier"Length of output: 2435
x/uibc/quota/intest/suite_test.go (1)
- 110-110: The change from
NewKeeperBuilder
toNewBuilder
in theinitKeeper
function call is consistent with the PR's objective. This update is part of the test suite, ensuring that the renaming is also reflected in the tests.x/uibc/uics20/ics4_wrapper_test.go (1)
- 55-55: The change from
NewKeeperBuilder
toNewBuilder
in theTestSendPacket
function call is consistent with the PR's objective. This update is part of the test suite, ensuring that the renaming is also reflected in the tests.x/uibc/module/module.go (2)
- 86-86: Renaming
KeeperBuilder
toBuilder
in theAppModule
struct aligns with the PR's objective to standardize naming conventions across the codebase.- 89-89: The update in the
NewAppModule
function to acceptBuilder
instead ofKeeperBuilder
is consistent with the renaming effort.x/uibc/uics20/ibc_module_test.go (1)
- 65-65: The change from
NewKeeperBuilder
toNewBuilder
in theTestIBCOnRecvPacket
function call is consistent with the PR's objective. This update is part of the test suite, ensuring that the renaming is also reflected in the tests.x/metoken/keeper/intest/keeper_test.go (1)
- 57-57: The change from
NewKeeperBuilder
toNewBuilder
in theinitTestSuite
function call is consistent with the PR's objective. This update is part of the test suite, ensuring that the renaming is also reflected in the tests.x/uibc/uics20/ibc_module.go (2)
- 27-27: Renaming
KeeperBuilder
toBuilder
in theICS20Module
struct aligns with the PR's objective to standardize naming conventions across the codebase.- 34-34: The update in the
NewICS20Module
function to acceptBuilder
instead ofKeeperBuilder
is consistent with the renaming effort.app/app.go (4)
- 284-284: The renaming of
UIbcQuotaKeeperB
fromuibcquota.KeeperBuilder
touibcquota.Builder
aligns with the PR's objective to standardize naming conventions across the codebase. This change enhances readability and consistency.- 464-464: The use of
ugovkeeper.NewBuilder
to instantiateUGovKeeperB
follows the PR's renaming convention and is correctly applied here. This change contributes to the overall goal of improving codebase consistency.- 497-497: Similarly, the instantiation of
MetokenKeeperB
usingmetokenkeeper.NewBuilder
adheres to the PR's renaming strategy. This consistent naming helps clarify the role of these components within the application.- 541-541: The renaming of
UIbcQuotaKeeperB
to useuibcquota.NewBuilder
in this context is consistent with the PR's objectives. It's good to see the renaming effort being applied thoroughly across the codebase.x/metoken/keeper/intest/msg_server_test.go (4)
- 610-610: The renaming from
KeeperBuilder
toBuilder
is consistent with the PR's objective and is correctly applied here.Ensure that the renaming does not inadvertently affect the functionality of the tests. It might be beneficial to verify that all tests still pass and behave as expected after the renaming.
- 707-707: The renaming from
KeeperBuilder
toBuilder
is correctly applied here as well.Similar to the previous comment, please ensure that the renaming does not affect the functionality of the tests.
- 1351-1351: Renaming applied correctly in the context of depegging tests.
As with the previous instances, verify that the functionality of the tests remains intact after the renaming.
- 1448-1448: The renaming from
KeeperBuilder
toBuilder
is applied correctly here as well.Please verify the functionality of the tests after the renaming.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
Small update to unify the name used in modules
Summary by CodeRabbit