[FEATURE] Diagnostic logging for conventions
Open
Nobody has claimed this yet.
.NET
feature: diagnostics
- Dominant language
- C#
- Stars
- 474
- Forks
- 65
- Avg merge
- 22h 25m
- Merged PRs (30d)
- 26
Description
Your suggestion
These are enhancements to the logging experience for debugging across PSRule conventions.
Alternatives
na
Additional context
No response
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 named. Start by locating the PSRule conventions logging path, then clarify which diagnostic events and logging behavior are required; the work is done only when those expectations and acceptance checks are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100