You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SDK module dependency graph below (generated from main 2023-01-09) shows that x/upgrade has only one dependent. If it can be removed it should be trivial to create a go.mod for this module and separate it from the SDK monolith.
x/upgrade has dependencies on the SDK modules shown below. As a part of this issue lets do a cursory review and remove them if trivial, or punt to the dependency's issue if not.
One thing depends on upgrade but from the things upgrade depends on is there anything we can remove? Is this part of the issue?
We don't strictly need to (since everything is still dependent on the SDK monolith) to make a standalone go module, but it's not a bad idea to remove that tech debt now if it's trivial to do so.
Ref: #11899
The SDK module dependency graph below (generated from main 2023-01-09) shows that x/upgrade has only one dependent. If it can be removed it should be trivial to create a go.mod for this module and separate it from the SDK monolith.
x/upgrade has dependencies on the SDK modules shown below. As a part of this issue lets do a cursory review and remove them if trivial, or punt to the dependency's issue if not.
List of To-dos when creating a
go.mod
: https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#gomodThe text was updated successfully, but these errors were encountered: