Skip to content

incompatible api diff result when one of property in model becomes not required #535

@lbxxxxx2a

Description

@lbxxxxx2a

if in new api version some property is not required anymore, new api is recognized as not compatible

old api schema definition:

"SomeDto": {
        "required": [
          "prop1",
          "prop2",
          "prop3"
        ], ...

new api schema definition:

"SomeDto": {
        "required": [
          "prop1"
        ], ...

Activity

typekpb

typekpb commented on Oct 30, 2023

@typekpb

same issue here

joschi

joschi commented on Dec 16, 2023

@joschi
Contributor

@lbxxxxx2a @typekpb Could you please provide a minimal set of OpenAPI specifications to demonstrate the issue?

added and removed on Jan 30, 2025
added this to the 2.2.0 milestone on Apr 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @joschi@typekpb@DrSatyr@lbxxxxx2a

        Issue actions

          incompatible api diff result when one of property in model becomes not required · Issue #535 · OpenAPITools/openapi-diff