microsoft / microsoft/PowerShell-FeatureFlags
Add a way to identify possible misconfigurations
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 24
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
There are some classes of errors which are not syntactic or semantic errors, but might indicate misconfiguration, and that could be considered warnings.
For example, the presence of stages that are not referenced by any feature could be considered worthy of a warning.
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 with the issue body and inspect the module's existing configuration validation and error-reporting behavior. Define how warnings should identify unreferenced stages and other possible misconfigurations, then document the expected warning behavior and tests needed to show it is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100