We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
Currently the library forces the user to define a list when using filter options even if only a single filter is applied:
{ "type": "object", "properties": { "created": { "type": "string", "filter": [ { "filter": "dateTime", "denyEmptyValue": true } ] } } }
Instead of the list allow the direct usage of an object to define a single filter with options:
{ "type": "object", "properties": { "created": { "type": "string", "filter": { "filter": "dateTime", "denyEmptyValue": true } } } }
The above currently crashes with a message unsupported filter denyEmptyValues which is not helpful.
unsupported filter denyEmptyValues
The text was updated successfully, but these errors were encountered:
Simplify object notation for single-filter usage (#27)
9fe70e7
wol-soft
No branches or pull requests
Currently the library forces the user to define a list when using filter options even if only a single filter is applied:
Instead of the list allow the direct usage of an object to define a single filter with options:
The above currently crashes with a message
unsupported filter denyEmptyValues
which is not helpful.The text was updated successfully, but these errors were encountered: