PowerShell / PowerShell/PSScriptAnalyzer
Add EditorConfig `.editorconfig` to project
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
Add EditorConfig .editorconfig to the project, like other PowerShell related repos already have.
- https://github.com/PowerShell/PowerShell/blob/master/.editorconfig
- https://github.com/PowerShell/PSResourceGet/blob/master/.editorconfig
- https://github.com/PowerShell/vscode-powershell/blob/main/.editorconfig
Proposed technical implementation details (optional)
Unify style, syntax, rules, linting, formatting across PowerShell related projects.
What is the latest version of PSScriptAnalyzer at the point of writing
Not relevant.
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 comparing the linked .editorconfig files from PowerShell, PSResourceGet, and vscode-powershell. Add a project-root .editorconfig with rules appropriate for PSScriptAnalyzer; done means the project has a consistent configuration aligned with the related repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 78/100