We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
(From #707 synthesis: one_not_null= should treat the absence of a key as equivalent to present and null.)
With this schema:
#@data/values-schema --- #@schema/type any=True #@schema/validation one_not_null=["rootdirectory", "path"] filesystem: rootdirectory: "" path: ""
this fails:
#@data/values --- filesystem: path: ""
Instead, it should succeed, treating rootdirectory as missing to be equivalent to it being present with a null value.
rootdirectory
null
The text was updated successfully, but these errors were encountered:
assert.one_not_null() treats missing keys as null
5d62146
Resolves #722
Show that one_not_null allows missing keys
017de83
Documents carvel-dev/ytt#722
pivotaljohn
Successfully merging a pull request may close this issue.
(From #707 synthesis: one_not_null= should treat the absence of a key as equivalent to present and null.)
With this schema:
this fails:
Instead, it should succeed, treating
rootdirectory
as missing to be equivalent to it being present with anull
value.The text was updated successfully, but these errors were encountered: