-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
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
required property in referenced response #102
Comments
Hi @gbkwiatt, thanks for raising this. What’s in your |
dataToken schema is just another properties which are fine in this case. dataToken:
type: object
properties:
errorMessage:
type: string
example: ''
errorCode:
type: string
example: ''
enum:
- ''
token:
type: string
example: hbGciOiJIUzI1NiIsInR5cCI6... validation error just says response should have required |
Okay, it looks like this isn't a bug, and your response schema is slightly different to your response body. Your response body has Try this response schema:
Does that resolve your error? (And if you get another error to do with |
I just had a look after sleep, and you are so right I don't know how I missed that, I was so certain config is there. Well It was there before but I must messed up on some point and in my head it was always there ;) Thank you for pointing it out. Again 'user errors' and your module is great, saves so much coding |
In this scenario my required properties are checked in the main response, not in nested config object. So it fails validation
yaml:
if I change
systemName
toconfig
on required, it passes validation. which menas doesnt matter where required is, it always checks from main response object ?The text was updated successfully, but these errors were encountered: