-
Notifications
You must be signed in to change notification settings - Fork 607
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
Add structs for Upgrades and Forks structs #1379
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1379 +/- ##
==========================================
- Coverage 19.82% 19.18% -0.64%
==========================================
Files 202 216 +14
Lines 27685 30693 +3008
==========================================
+ Hits 5489 5889 +400
- Misses 21175 23723 +2548
- Partials 1021 1081 +60
Continue to review full report at Codecov.
|
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.
Nice work!!!
as is the case for all osmosis `Fork`s, then all logic changes must be height-gated or in the `BeginForkLogic` code. | ||
|
||
```go | ||
type Upgrade struct { |
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.
nit: I think these code snippets are likely to go out of sync with the actual code overtime
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.
Hopefully they never update O_O
Closes: #1375
What is the purpose of the change
Simplifies a lot of the upgrades management logic / boilerplate. The goal is that every new upgrade should from the app.go level, just require a one line update. And all the complexity would otherwise be held to within each upgrades module.
This PR is marked as draft until Changelog update + docs update to the
app/upgrades
README.Brief change log
Testing and Verifying
This should be covered by the existing test for the v4 upgrade, which tests that upgrade handler execution happens.
Documentation and Release Note
Unreleased
section inCHANGELOG.md
? Needs to be Donex/<module>/spec/
) / Osmosis docs repo / not documented)