Closed isZumpo closed 2 months ago
I agree that linter should not produce errors, I just fixed all of them for now.
I replaced this "//logger.Info("main", "Successfully closed database")" with standard log.Printf() and enabled prints again. However I am not very happy with current logging methods, I would like to have multiple logging levels and easy way to toggle them. I need to overhaul this at some point.
Oh very nice! I see that the gate is sucessfull now. Then I will go ahead and close this issue.
Yes, I agree. Multiple levels of loggning would be great. Then could log most things without polluting the logs.
I would like to see all linting issues resolved such that the linting gate can actually be useful. I could probably go through and fix most of them quite quickly. However, I wonder which strategy should be used to deal with "unused" code such as variables and in some cases empty branches.
Unusued variables For the unused variables etc, should we just go ahead and remove them? Or should we comment them out? I would prefer removing them since we can always go back in git history and bring them back if desired, while commenting bloats the code...
Empty branches From a very quick look, many of these appears to be commented out logging. For example this file in internal/analysis/realtime.go:
Do we want to enable the logging again?
These are currently all linting issues: