You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank you for a great library. I've found it really useful and its 'options' features is the one which I could not find in other libraries.
I was working with different schema validations for a project. Let's say, my whole JSON body is empty and the schema defines all the fields are optional.
Is there a way to define that even though all the fields are optional, at least one (any of it) should be present in the body and the body should not be empty?
If my JSON body has two fields A and B and the schema defines A and B as optional. Is there a way to define that if A is present, then, B is required?
It may not be a bug, but I could find the documentation supporting such features.
Thank you for your time.
Neeraj
The text was updated successfully, but these errors were encountered:
First of all, thank you for a great library. I've found it really useful and its 'options' features is the one which I could not find in other libraries.
I was working with different schema validations for a project. Let's say, my whole JSON body is empty and the schema defines all the fields are optional.
It may not be a bug, but I could find the documentation supporting such features.
Thank you for your time.
Neeraj
The text was updated successfully, but these errors were encountered: