PowerShell / PowerShell/PSScriptAnalyzer
Support `.config` project directory
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Summary of the new feature
To declutter a project root directory I'd like the ability to put the PSSA config file inside a .config directy, like suggested here (more details):
- Proposal: https://dot-config.github.io/, https://github.com/pi0/config-dir
- Support tracker: https://github.com/pi0/config-dir/discussions/6
One can of course override the config path, but native support for this would be neat.
Proposed technical implementation details (optional)
If running PSSA from project root I'd like it to automatically pick up the config in .config/.
What is the latest version of PSScriptAnalyzer at the point of writing
v1.24.0
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
Start by locating the repository code that resolves the PSScriptAnalyzer configuration path when invoked from a project root, then inspect how explicit config-path overrides are handled. Implement discovery of a config file in .config/ without changing the override behavior, and verify that running PSSA from the project root finds it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100