False positives for rule 1007 RemovedClientParameter when using typespec-autorest
- 主要语言
- C#
- 星标
- 290
- 派生
- 50
- 平均合并
- 5 天 13 小时
- 30 天内合并 PR
- 5
描述
Hi, I'm working on https://github.com/Azure/azure-rest-api-specs-pr/pull/15631 and there are a bunch of breaking changes reported for [rule 1007](https://github.com/Azure/openapi-diff/blob/master/docs/rules/1007.md). According to https://github.com/Azure/typespec-azure/issues/3795 , these are false positives. Are these false positives? Can the rule be updated to eliminate these false positives?
How can I suppress these false positives? I've tried a few options without luck:
``` yaml
suppressions:
- code: RemovedClientParameter
reason: typespec-autorest puts the parameters in each operation
from: vmware.json
```
``` yaml
directive:
- suppress: RemovedClientParameter
reason: typespec-autorest puts the parameters in each operation
from: vmware.json
```
贡献指南
调研方向
Start with docs/rules/1007.md and the linked TypeSpec Azure issue, then reproduce the reported RemovedClientParameter findings using vmware.json and the referenced pull request. Determine whether these are false positives and how suppression is intended to work; done means a verified rule correction or a documented working suppression, with regression coverage if an applicable test exists.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- csharp, openapi
- 领域
- api, cli, tooling
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 28/100