PowerShell / PowerShell/PSScriptAnalyzer
Improve configuration
Open
Nobody has claimed this yet.
Consider - 2.0
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Configuration of PSSA2 should be easier.
In particular:
- Misconfigurations should present a useful error to users about expectation vs what was given
- Configuration should take a list of rule configurations and implicitly turn them into a dictionary, rather than require null dictionary entries
- Perhaps add more here
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. Begin by locating PSSA2's configuration handling; done means useful expectation-versus-input errors and accepting rule configurations as a list without null dictionary entries, while the broader "perhaps add more" request remains to be scoped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100