PowerShell / PowerShell/PSScriptAnalyzer
Proposal: Basic Telemetry for PSSA
未关闭
还没有人认领这个 Issue。
Issue - Discussion
- 主要语言
- C#
- 星标
- 2.2k
- 派生
- 414
- 平均合并
- 13 小时 1 分钟
- 30 天内合并 PR
- 2
描述
PSScript Analyzer Proposed Telemetry
Goal
To better understand how PSSA is being used both within PSES and in isolation in order to make informed investments in PSSA 2.0.
Questions
- What versions of PowerShell are being used with PSSA? What versions of PowerShell should we continue to support?
- What tasks are PSSA currently being used to accomplish?
- To what extent is PSSA being used inside vs. outside of PSES? Which of these experiences is most important to optimize?
- To what extent are custom rules vs. built in rules being used?
- What is the proportional use of PSSA as a formatter vs "analyzer"?
- To what extent are the compatibility rules being used? Which platforms are being targeted the most?
- What rules are being turned off? What rules should we strip out?
- Which rules are causing the largest performance delays?
Proposed Metrics
- Version of PowerShell
- Inside vs Outside of PSES
- CI usage/environment type
- Time for each rule to complete
- Count of:
- Known formatter type rules
- Known analyzer type rules (tally for each one)
- Custom rules (not on our known list)
- Known compatibility profiles (tally for each one)
- Use of a configuration
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
该 issue 未指定任何文件、测试或入口点。首先,将列出的问题和建议的指标转化为 PSSA 的遥测设计,涵盖在 PSES 内部和外部的使用。确定收集所提议指标的范围和实施计划后,即视为完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- powershell
- 领域
- analytics, observability
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100