napcok/calamares
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

CI: update documentation of debug-levels

Browse Source
This commit is contained in:
Adriaan de Groot 2019-06-11 10:45:31 +02:00
parent 0a1b27fcfa
commit 94bea9baaf
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
ci/HACKING.md
View File

@ -184,14 +184,18 @@ connect( m_moduleManager, &Calamares::ModuleManager::modulesLoaded, [this]
Debugging Debugging
--------- ---------
Use `cDebug()` and `cLog()` from `utils/Logger.h`. You can pass a debug-level to Use `cDebug()` and `cLog()` from `utils/Logger.h`. You can pass a debug-level to
either macro (1 is debugging, higher is less important). Use `cLog()` for warning either macro (6 is debugging, higher is less important). Use `cWarning()` for warning
messages. It is recommended to add *WARNING* as the first part of a warning messages (equivalent to level 2) and `cError()` for errors (level 1). Warnings
message. and errors will add relevant text automatically. See `libcalamares/utils/Logger.h`
for details.
For log messages that are continued across multiple calls to `cDebug()`, For log messages that are continued across multiple calls to `cDebug()`,
in particular listing things, conventional formatting is as follows: in particular listing things, conventional formatting is as follows:
* End the first debug message with ` ..` * End the first debug message with ` ..`
* Indent following lines with ` ..` * Start the next debug message by outputting `Logger::SubEntry`
For single-outputs that need to be split across multiplt lines,
output `Logger::Continuation`.
Commit Messages Commit Messages