[Rule 1005] RemovedPath rule should account for deprecation mechanism when available
Open
bug
planned
- Dominant language
- C#
- Stars
- 290
- Forks
- 50
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 5
Description
Correctly deprecated path / operation should not be reported as the breaking change with error severity
Contributor guide
Research direction
Start by locating the implementation and tests for Rule 1005, then trace how deprecation metadata is represented for paths and operations. Compare the current result for a deprecated removal with the expected breaking-change severity; done means deprecated removals are not reported with error severity when the deprecation mechanism is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100