Files
ClassicAssist.Avalonia/.qoder/repowiki/knowledge/en/No Centralized Logging System/No Centralized Logging System.md
T
Beyhan Oğur d5f52cc3d3 first commit
2026-09-03 04:45:36 +03:00

9 lines
1.2 KiB
Markdown

---
kind: logging_system
name: No Centralized Logging System
category: logging_system
scope:
- '**'
---
This repository does not implement a centralized logging system. There is no dedicated logger framework (such as log4net, Serilog, NLog, or Microsoft.Extensions.Logging) and no shared logging infrastructure in the ClassicAssist.Shared core library. Instead, diagnostic output is scattered ad hoc across the codebase using primitive mechanisms: `Console.WriteLine` calls for basic tracing (e.g., platform detection, network errors, exception dumps), `System.Diagnostics.Debug.WriteLine` / `Trace.WriteLine` for development-time diagnostics, and occasional direct file writes via `File.WriteAllText`. Some logging calls are commented out (e.g., `//Log.Info(...)` in IncomingPacketHandlers.cs), indicating prior attempts at structured logging that were removed. The DebugWindow UI provides an in-process text buffer for runtime messages but does not back onto any persistent log sink. As a result, there are no log levels, no structured fields, no configurable sinks, and no consistent conventions — developers should be aware that adding a proper logging abstraction would require replacing these scattered calls with a unified approach.