-
Notifications
You must be signed in to change notification settings - Fork 103
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(x/ecocredit): rename ecocredit core functionality to base #1447
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1447 +/- ##
==========================================
- Coverage 78.48% 78.45% -0.03%
==========================================
Files 238 238
Lines 18439 18448 +9
==========================================
+ Hits 14471 14473 +2
- Misses 3126 3130 +4
- Partials 842 845 +3
|
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.
pre-approving
found a few lingerings of "core":
- variable name
coreQuerier
should now bebaseQuerier
https://github.com/regen-network/regen-ledger/blob/ryan/rename-core-to-base/x/ecocredit/module/module.go#L269 - comment
ecocredit core
should now beecocredit base
https://github.com/regen-network/regen-ledger/blob/ryan/rename-core-to-base/x/ecocredit/genesis/genesis.go#L250 - varable name
coreQryClient
should now bebaseQryClient
https://github.com/regen-network/regen-ledger/blob/ryan/rename-core-to-base/x/ecocredit/marketplace/simulation/operations.go#L271 - theres a few gas iteration descriptions that still path to "core" in msg server functions create_class, retire, send, update_class_issuers, marketplace.sell
- all our codecs still register the types with regen.core, but i am unsure if that should change/could cause problems? 🤔 do you have any insight on that?
not sure if all of these should be addressed here, but figured i'd point em out just in case 👍🏻
As far as I can tell, this should be ok to update. Might require a change for app developers so added a changelog entry for this specifically. This should probably not have been |
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
Ref: #1196, #1429
Finish renaming core to base following #1429.
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...
!
to the type prefix if API or client breaking changeCHANGELOG.md
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.
I have...
!
in the type prefix if API or client breaking change