8000
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
create a cfgu file.
add a key with enum: [...any values you wish]
enum: [...any values you wish]
validate the cfgu with an empty object.
try to explicitly add required: false
required: false
The key is not required, so an empty value should be valid.
validate the cfgu with an empty object. -> should be valid.
try to explicitly add required: false. -> should be valid.
Seems like required: false is ignored, even when we explicitly mention it.
JSONSchema supports enum not to be required. For example, check this schema:
{ "type": "object", "properties": { "a": {"type": "string", "enum": ["a","b"]} } }
an empty object is a valid value for this schema.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Current Behavior
create a cfgu file.
add a key with
enum: [...any values you wish]
validate the cfgu with an empty object.
try to explicitly add
required: false
Expected Behavior
The key is not required, so an empty value should be valid.
To Reproduce
create a cfgu file.
add a key with
enum: [...any values you wish]
validate the cfgu with an empty object. -> should be valid.
try to explicitly add
required: false
. -> should be valid.Context
Seems like
required: false
is ignored, even when we explicitly mention it.JSONSchema supports enum not to be required.
For example, check this schema:
an empty object is a valid value for this schema.
The text was updated successfully, but these errors were encountered: