OpenAPITools / OpenAPITools/openapi-diff
Deleted or renamed properties are marked as backwards compatible
Open
Nobody has claimed this yet.
Breaking/Non-Breaking classification
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 190
- PR merge metrics
- No merged PRs in 30d
Description
Hello folks,
i am testing your library as a maven plugin with version: 'org.openapitools.openapidiff:openapi-diff-core:2.1.0-beta.11' and discovered that the following changes do not result in failure due to backwards incompatibility even though they should, right?
- Removing properties from schemas
- Renaming properties
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 reproducing the report with openapi-diff-core 2.1.0-beta.11 and two OpenAPI specifications that remove or rename schema properties. Trace the comparison used by the Maven plugin and verify that each change is classified as backward-incompatible, with regression coverage for both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100