Add channel # to rhs_write XML messages
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 439
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
Currently messages coming from the trace, log and write RHS functions all look the same to print handlers.
As such the "channel" functions more like a on/off flag rather than what you would normally call a channel.
If you add a channel attribute to rhs_write XML messages when they come from log, then print handlers will be able to use that to determine how to display or handle the message.
You might want to do something similar with trace
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 locating the trace, log, and write RHS functions and the code that emits their rhs_write XML messages. Check how print handlers consume these messages, then add a channel attribute for messages from log and assess whether trace needs the same treatment. Done means handlers can distinguish the message source from the XML output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100