PowerShell / PowerShell/PSScriptAnalyzer
Update/standardize the internal custom `VariableAnalysis` classes
还没有人认领这个 Issue。
- 主要语言
- C#
- 星标
- 2.2k
- 派生
- 414
- 平均合并
- 13 小时 1 分钟
- 30 天内合并 PR
- 2
描述
This addresses technical debt.
... the
VariableAnalysisclasses that were forked from PowerShell's own classes 4 years ago. Those classes were not updated since and have small bugs that leads to certain types of analysis not being possible. Unfortunately, the original maintainers have taken only a subset of it and added a lot of custom code to it. I once tried to just delete it and replace it with the code from PowerShell and some of the challenges were that SMA are very entangled with each other in terms of dependencies and it compiles against .Net Core, but PSSA compiles against .Net Standard.
(https://github.com/PowerShell/PSScriptAnalyzer/pull/1277#issuecomment-508929230)
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先阅读 PowerShell/PSScriptAnalyzer#1277 中链接的讨论,并确定内部的 VariableAnalysis 类及其依赖项。在考虑 .NET Core 和 .NET Standard 编译目标的同时,将 fork 的类与 PowerShell 的版本进行比较。完成的标准是:在不破坏分析器的情况下,解决技术债务、已知的分析错误以及依赖项或框架限制。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- csharp, powershell
- 领域
- tooling
- Issue 类型
- 重构
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 20/100