Skip to content

Unify logging #146

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

Open
matthijskooijman opened this issue May 9, 2016 · 1 comment
Open

Unify logging #146

matthijskooijman opened this issue May 9, 2016 · 1 comment
Labels
topic: code Related to content of the project itself type: enhancement Proposed improvement

Comments

@matthijskooijman
Copy link
Collaborator

Currently, there are a few ways in which the logging happens, or can be influenced:

  • There is a Logger instance, that can output human-readable or structured log entries (I think the latter are read by the IDE and parsed in some way?). Each of these log entries has a log level, which is currently ignored for at least the human readable logger.
  • There is a -verbose flag that enables printing of commands and some other verboseness
  • There is a -debug-level flag that sets a debug level, of which it seems that only level 0, level 5 and level 10 actually change the output.

It seems sane to have a single log level option, which defines how much output is shown. The current -verbose and -debug-level flags can probably be converted into a value in that log level.

Also, there are currently some things printed unconditionally, even with no debug level or verbose mode set. When running go test without -v, you might want to suppress this output altogether, to make it easier to list failed testcases, without hiding them in informational output. This could be implemented using this single log level, by adding a "NONE" log level that suppresses all output.

@matthijskooijman
Copy link
Collaborator Author

I just noticed #12, which is certainly related.

@per1234 per1234 added topic: code Related to content of the project itself type: enhancement Proposed improvement labels Oct 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: code Related to content of the project itself type: enhancement Proposed improvement
Projects
None yet
Development

No branches or pull requests

2 participants