Code quality: fmt.Println/Printf debug output in production code #40

New issue

Open

opened 2026-04-04 17:51:38 +00:00 by stu · 0 comments

stu commented

2026-04-04 17:51:38 +00:00

Owner

Locations

internal/modules/handlers.go:16-101 � Multiple fmt.Println() calls for debug logging
internal/ui/components.go:269, 275, 287 � fmt.Printf() in the drag-and-drop handler

Impact

Pollutes stdout with debug noise in production builds. Should use the logging package with an appropriate category (logging.CatUI, logging.CatSystem, etc.) at Debug level so output is gated by the log level setting.

Fix

Replace all fmt.Println/fmt.Printf in these files with logging.Debug(logging.CatXxx, ...) calls.

## Locations 1. `internal/modules/handlers.go:16-101` � Multiple `fmt.Println()` calls for debug logging 2. `internal/ui/components.go:269, 275, 287` � `fmt.Printf()` in the drag-and-drop handler ## Impact Pollutes stdout with debug noise in production builds. Should use the `logging` package with an appropriate category (`logging.CatUI`, `logging.CatSystem`, etc.) at Debug level so output is gated by the log level setting. ## Fix Replace all `fmt.Println`/`fmt.Printf` in these files with `logging.Debug(logging.CatXxx, ...)` calls.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

leak_technologies/VideoTools#40

No description provided.

Rows
Columns