fix(logging): correct log level severity order

Reverse enum so lower values = less severe, higher = more severe.
This makes the filter check (level < min_log_level) work correctly.

- DEBUG (0) - least severe, filtered by default
- INFO (1) - default minimum level
- WARN (2) - warnings and above
- ERROR (3) - most severe, always shown

Fixes incorrect filtering where ERROR/WARN were being blocked.
This commit is contained in:
2026-02-14 17:22:39 +01:00
parent 70e9ec2fc3
commit 70d50dda92
+3 -3
View File
@@ -8,10 +8,10 @@ extern "C" {
#endif
typedef enum {
STK_LOG_ERROR,
STK_LOG_WARN,
STK_LOG_DEBUG,
STK_LOG_INFO,
STK_LOG_DEBUG
STK_LOG_WARN,
STK_LOG_ERROR
} stk_log_level_t;
void stk_set_log_output(FILE *fp);