Skip to content

False Negative when comparing schemas missing optional fields #352

Open
@Bento007

Description

@Bento007

When a schema is uploaded top AWS, optional fields that are missing are added to the schema with empty
values. This may cause the schemas to not match when compared even though they are functionally equivalent. This
problem has been observed when a local schema defines a facet that does not contain attribute_rules. After the
schema is published, the schema contained "attribute_rules": {}. This resulted in a false negative indicating that
the schemas did not match.

Activity

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

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions