microsoft / microsoft/VFSForGit
Q: The project seems to avoid using a dependency injection framework. Why?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 474
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
Currently, initialization code is all over the place, which makes dependency tracking and lifecycle management hard sometimes. Given the abundance of available DI frameworks out there, is there a reason, why VFS4G team decided not to use one?
Also, somewhat related: The team uses their own JsonTracer class and related code, as opposed to taking an existing logging framework, like NLog, log4net or Serilog. Is there a reason for that?
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
No files, tests, or entry points are identified. Review the project's initialization code and the JsonTracer-related code to understand current dependency and lifecycle handling; a complete outcome would need a decided direction and documented rationale for retaining or changing these approaches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- developer-experience, observability
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100