Logging to custom stream or file
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Would it be possible to add the ability to log to a custom stream or file?
This would be useful for CLI applications where the user interacts with the application (e.g., application that uses dialogs, REPLs, and TUI application).
Right now, it seems, `roarr` wouldn't be usable for such applications.
This also would enable to display the logs in a separate terminal window (e.g., `tail $log_file | roarr`), which itself would be a useful feature (e.g., if you are only interested in the logs when something bad happens).
With this approach, it also would be possible to change the configuration of `roarr` CLI (e.g., changing its filter configuration) while the main application is still running.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the roarr CLI and the current logging output path to determine how logs are written today. Define the behavior needed for directing logs to a custom stream or file, including how the CLI can read and filter that output while the main application continues running. Done means CLI applications can use the feature without interfering with their interactive output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100