Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

False Negative when comparing schemas missing optional fields #352

Open
Bento007 opened this issue Nov 21, 2019 · 0 comments
Open

False Negative when comparing schemas missing optional fields #352

Bento007 opened this issue Nov 21, 2019 · 0 comments
Labels
bug Something isn't working

Comments

@Bento007
Copy link
Member

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.

@Bento007 Bento007 added the bug Something isn't working label Nov 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant