Log levels and filtering
Open
Nobody has claimed this yet.
improvement
just do it
lang: c++
- Dominant language
- Python
- Stars
- 14.4k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
We already have log levels, but all messages are printed to stdout right now.
This is the stdout sink of the logging subsystem.
Filtering for log origin is prepared, but not implemented.
- Implement more log sinks, for example for a specific unit, so we can print its messages in a console window flying above its head (#48)
Contributor guide
No contributing guide indexed for this repository
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 logging subsystem's stdout sink and the prepared filtering for log origin. Review issue #48 for the intended unit-specific console window behavior. Done means additional log sinks can route messages for a specific unit instead of sending every message to stdout.
Written by the indexing model from the issue text.
Assessment
- Domain
- game-dev, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100