mirror of https://github.com/stashapp/stash.git
214a15bc40
* Add a space after // comments For consistency, the commentFormatting lint checker suggests a space after each // comment block. This commit handles all the spots in the code where that is needed. * Rewrite documentation on functions Use the Go idiom of commenting: * First sentence declares the purpose. * First word is the name being declared The reason this style is preferred is such that grep is able to find names the user might be interested in. Consider e.g., go doc -all pkg/ffmpeg | grep -i transcode in which case a match will tell you the name of the function you are interested in. * Remove old code comment-blocks There are some commented out old code blocks in the code base. These are either 3 years old, or 2 years old. By now, I don't think their use is going to come back any time soon, and Git will track old pieces of deleted code anyway. Opt for deletion. * Reorder imports Split stdlib imports from non-stdlib imports in files we are touching. * Use a range over an iteration variable Probably more go-idiomatic, and the code needed comment-fixing anyway. * Use time.After rather than rolling our own The idiom here is common enough that the stdlib contains a function for it. Use the stdlib function over our own variant. * Enable the commentFormatting linter |
||
---|---|---|
.. | ||
hook.go | ||
logger.go | ||
plugin.go | ||
progress_formatter.go |