-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Remove alias.go usage #6311
Comments
I fully support this proposal as I was never a fan of the alias approach. Now that we no longer have |
Hi, can I work on this? |
Sure thing @dauTT. I’d recommend you to do it one module per PR at a time. Otherwise the changes would be massive |
I will track the progress of this task here:
|
nice table! To make things easier you don't need to create issues for each one. You can just ref this issue and close it when they are all done. |
Great 👍 . One thing I often encounter with aliases is that they introduce unnecessary cyclic dependencies sometimes. Often, I have to manually use |
All the sub tasks above are completed. I think we can close this issue. 😄 |
Sub modules in IBC need to have alias.go removed (03-connection, 04-channel etc) |
there seems to be one last straggler: cosmos-sdk/x/auth/vesting/alias.go Line 1 in bf8809e
|
Summary
Remove
alias.go
files in favor of more verbose import names such as<modulename>types
and<modulename>keeper
Problem Definition
alias.go
can be useful when managing access to internal types, but the sdk does not use internals anymore. Currently I believe its usage is purely aesthetic.I think verbose import names are especially useful for new developers to the codebase who might not be familiar with the differences between
keeper/
andtypes/
. Verbose import names indicate clearly which package the type comes from. I've also foundalias.go
to be out dated do to lack of enforcement of updating it on unused types (perhaps from the types being directly imported).Proposal
Remove
alias.go
, use verbose import names. Remove from module design spec as well.For Admin Use
The text was updated successfully, but these errors were encountered: