Project
vgrep
Description
The codebase uses println! for all output (264 occurrences) instead of a structured logging framework. This makes it impossible to:
- Control log levels
- Filter output
- Log to files
- Integrate with observability tools
- Debug in production
Error Message
Debug Logs
System Information
- Bounty Version: 0.1.0
- OS: Ubuntu 24.04 LTS
- Rust: 1.75+
Screenshots
No response
Steps to Reproduce
- Run any vgrep command
- Output goes directly to stdout
- No way to control verbosity
- No way to log to file
- No timestamps on output
Expected Behavior
- Use
tracing or log crate for all output
- Configurable log levels (error, warn, info, debug, trace)
- Option to log to file
- Structured JSON logging for machine parsing
- Timestamps on log entries
Actual Behavior
- All output via
println!
- No log levels
- No log file support
- No machine-readable format
- No timestamps
Additional Context
No response
Project
vgrep
Description
The codebase uses
println!for all output (264 occurrences) instead of a structured logging framework. This makes it impossible to:Error Message
Debug Logs
System Information
Screenshots
No response
Steps to Reproduce
Expected Behavior
tracingorlogcrate for all outputActual Behavior
println!Additional Context
No response