PowerShell / PowerShell/PowerShellEditorServices
Investigate source generators to improve some patterns
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 767
- Forks
- 266
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 1
Description
Dependency injection and "interface everything" can be very useful patterns but they also increase maintenance and debug complexity. Source generators can help by making references actually followable (DI) or reducing manual interface upkeep (interface everything).
For example:
https://github.com/DevTeam/Pure.DI
https://github.com/beakona/AutoInterface
Far from important though, marking up for grabs
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
The issue names no files, tests, or entry points. Start by reviewing the Pure.DI and AutoInterface examples and the repository architecture, then determine whether source generators address the described DI and interface-maintenance concerns; done would require an agreed, actionable direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100