PowerShell / PowerShell/PSScriptAnalyzer
Should the 'Microsoft.Windows.PowerShell.ScriptAnalyzer' namespace/assembly names be renamed to 'Microsoft.PowerShell.ScriptAnalyzer' ?
Open
Nobody has claimed this yet.
Area - Build
Consider - 2.0
Issue - Enhancement
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Question as per title. This would be a breaking change. What do you think @JamesWTruher
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 reviewing the namespace and assembly names described in the issue, along with the eight-comment discussion, to determine whether the proposed rename is wanted. Because this is a breaking-change question with no files, tests, or implementation scope identified, done is not defined until the project reaches a decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100