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
Hi! I think I have encountered a problem that I don't know how to resolve.
If I declare a property of type Object inside the top level object of the "body" schema:
body: t.Object({ name: t.String(), pvp: t.Numeric(), categoryId: t.Optional(t.Numeric()), useless: t.Optional( t.Object({ useless1: t.String(), useless2: t.Numeric() }) ) }),
That endpoint becomes impossible to reach if, in this case the useless property, is totally absent from the JSON body
I don't know how the internals work of course, but may a conditional access (?.) in the validation code could fix this.
The text was updated successfully, but these errors were encountered:
This should be fixed in 0.7 by the removal manual extractor #103.
Let me know if the issue still persists
Sorry, something went wrong.
This is fixed in [email protected]
No branches or pull requests
Hi! I think I have encountered a problem that I don't know how to resolve.
If I declare a property of type Object inside the top level object of the "body" schema:
That endpoint becomes impossible to reach if, in this case the useless property, is totally absent from the JSON body
I don't know how the internals work of course, but may a conditional access (?.) in the validation code could fix this.
The text was updated successfully, but these errors were encountered: