Skip to content

Change detected when uniqueItems is explicitely set to false while it is the default #75

@gricher-crto

Description

@gricher-crto

As per the specification, uniqueItems defaults to false (see https://www.learnjsonschema.com/draft6/validation/uniqueitems/)
However, comparing two document specifications only different in the fact that the first omit uniqueItems (implicitly false) while the second include the explicit uniqueItems: falsestatement returns the following kind of warning:

 {
    "Severity": "Warning",
    "Message": "The new version has a different 'uniqueItems' value than the previous one.",
    "OldJsonRef": "#/paths/~1test/post/requestBody/content/application~1json/schema/uniqueItems",
    "NewJsonRef": "#/paths/~1test/post/requestBody/content/application~1json/schema/uniqueItems",
    "OldJsonPath": "#/paths/~1test/post/requestBody/content/application~1json/schema/uniqueItems",
    "NewJsonPath": "#/paths/~1test/post/requestBody/content/application~1json/schema/uniqueItems",
    "Id": 1036,
    "Code": "ConstraintChanged",
    "Mode": "Update"
  }

I would expect that no change is returned in this case

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions