Be able to pass an IO for our logger to write to.
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 1.2k
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
e.g. Roast::Log(msg, to: custom_io)
This would allow us to do a capture_io test helper that creates unique IO's for individual invocations or whole test suites.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Roast::Log entry point and its logger implementation. Check how current logging destinations are selected, then add coverage for passing a custom IO and confirm that messages are written to that IO without disrupting existing logging behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100