No structured logging system #105

Closed
opened 2026-04-04 18:42:27 +02:00 by shahondin1624 · 0 comments
Owner

Description

The codebase has no structured logging. Errors are silently caught or printed to stdout. Debugging issues across platforms (Android, Desktop, Web, iOS) requires a consistent logging solution.

Expected Behavior

  • Use a multiplatform logging library (e.g., Napier, Kermit)
  • Log errors, warnings, and important state transitions
  • Platform-appropriate log output (Logcat on Android, console on Desktop/Web)

Acceptance Criteria

  • Multiplatform logging library integrated
  • Error catches include log statements with context
  • Log levels used appropriately (ERROR, WARN, INFO, DEBUG)
  • Logging works on all target platforms
## Description The codebase has no structured logging. Errors are silently caught or printed to stdout. Debugging issues across platforms (Android, Desktop, Web, iOS) requires a consistent logging solution. ## Expected Behavior - Use a multiplatform logging library (e.g., Napier, Kermit) - Log errors, warnings, and important state transitions - Platform-appropriate log output (Logcat on Android, console on Desktop/Web) ## Acceptance Criteria - [ ] Multiplatform logging library integrated - [ ] Error catches include log statements with context - [ ] Log levels used appropriately (ERROR, WARN, INFO, DEBUG) - [ ] Logging works on all target platforms
shahondin1624 added the priority:should-havetype:architecture labels 2026-04-04 18:42:27 +02:00
Sign in to join this conversation.