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

should "default" values be added to result JSON? should "default" values be ignored by "required" ? #72

Open
abogosyan opened this issue Sep 5, 2018 · 1 comment

Comments

@abogosyan
Copy link

SUBJ?

@andreineculau
Copy link
Member

q1: v4 draft doesn't mention it https://tools.ietf.org/html/draft-fge-json-schema-validation-00#section-6.2
currently we do not alter the input JSON in any way and doing so has implications on performance afaics. but it is a potential improvement

q2: https://tools.ietf.org/html/draft-fge-json-schema-validation-00#section-5.4.3 as far as my interpretation of the v4 draft is that a field is required, no matter if it has a default spec

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants