-
Notifications
You must be signed in to change notification settings - Fork 608
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
chore: app package housekeeping #1125
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1125 +/- ##
==========================================
+ Coverage 19.90% 19.92% +0.01%
==========================================
Files 200 200
Lines 25498 25503 +5
==========================================
+ Hits 5076 5081 +5
Misses 19515 19515
Partials 907 907
Continue to review full report at Codecov.
|
app/app.go
Outdated
|
||
// Osmosis application prarmeters |
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.
Do you think we should revert these comments / the prior ordering of imports here?
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.
You mean keep them?
Import blocks aren't meant to be annotated. If you think devs would really find them useful, I can revert :)
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.
@faddat was the one who added them, presumably he's found it helpful when explaining app.go's to people.
We could put the same comments in the AppKeepers struct though, I don't think theres anything particularly important about this info being in the imports
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.
Gotcha, yeah I mean I guess I can see how they're helpful, but then a few questions/points arise:
- Do I now too have to keep these up to date and add them for any new imports (burden on me)
- Import blocks become extremely verbose
@faddat are you against removing these annotations?
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! I'm fine with removing the import annotations, and moving the equivalent annotations elsewhere in structs directly
@ValarDragon can you merge this whenever you get a chance? |
Description
Some general linting and housekeeping to the
app
package. Changes are meant to be non-contentious and ultimately make the code and style consistent and most importantly legible.Feel free to close/deny if deemed too contentious :)
For contributor use:
docs/
) or specification (x/<module>/spec/
)Unreleased
section inCHANGELOG.md
Files changed
in the Github PR explorer