rust-cli / rust-cli/env_logger
suggestion: Make directives public in env_filter
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.1k
- Forks
- 149
- Avg merge
- 2h 42m
- Merged PRs (30d)
- 4
Description
My use case is using env_filter to configure another logger (pyo3_log). Right now I can only use the top-level filter but if I could access each directive in the Filter instance, it would be trivial to use it in every logger that doesn't have its own utility to parse standard directives.
If the maintainers think this is a good idea, I'm glad to do the actual work.
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 inspecting the env_filter entry point and the Filter representation, then trace how directives are parsed and stored. Determine a public way to access each directive without assuming an API shape; done means consumers such as pyo3_log can retrieve individual directives, with coverage for the exposed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100