-
Notifications
You must be signed in to change notification settings - Fork 340
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
Migration code standartization #1160
Comments
Known example of adhoc dymension/x/sequencer/migrations.go Lines 1 to 45 in 76aa1e1
|
I think it's fine to have everything in app/upgrades/v4 Here are more specific issues |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we have some migration code, with similiar logic (e.g migrating params) written in
upgrade.go
and some in ad-hoc migration files.we need to have a standard place for writing migration code and agree which code, if any, goes directly to the
upgrade.go
module.The text was updated successfully, but these errors were encountered: