microsoft / microsoft/RecursiveExtractor
Refactor logging to use ILoggerFactory pattern
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C#
- Stars
- 220
- Forks
- 35
- Avg merge
- 20d 1h
- Merged PRs (30d)
- 1
Description
Allows logger to be passed in from dependent callers.
For logging directly from RecursiveExtractor we should use Serilog.
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 locating the RecursiveExtractor logging entry points and existing ILoggerFactory usage. Review how dependent callers currently provide logging and how direct logging is handled with Serilog; done means the requested logging pattern is applied consistently and the affected behavior is covered by the project's available checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100