Open xrn opened 2 years ago
Now I see that when I am making
"properties": {
"name": {
"description": "Tenant Name",
"type": ["string","null"]
}
}
Documentation is generating but there is still bug
"properties": {
"name": {
"description": "Tenant Name",
"type" : "object"
}
}
Same issue here. Its a real headache when you are trying to create documentation for you api.
Same issue, very incovenient.
with data type as string you can not define nullable values
type: string nullable: true
just don't work, You have to define something like this "type": ["string","null"]
with data type as string you can not define nullable values
type: string nullable: true
just don't work, You have to define something like this "type": ["string","null"]
and if i got a property with only nullable
without type
?
"type": ["string","null"] or "type": ["null"] did work
Hi,
Are there any plans to take action on this topic?
for now the only way to make the validation/documentation working is to do this acc. to the @xrn proposal:
https://github.com/awslabs/aws-api-gateway-developer-portal/issues/544#issuecomment-1490671915
However, the resulting type in documentation is object
which is obviously not valid.
Hi,
I want to report bug with API Gateway 3.0 yaml/json export. When I will use in my model type: null like
generated OpenAPI3.0 will be
Which if ofc is incorrect. When I will use different form
OpenApi documentation will not generate at all. Could you advice what to do in this case or this is just bug? Due to this issue I am not able to show that we can accept sting as well as null (field is nullable)
Advice: From what I see you are using standard 3.0.1 - from my understanding you should update as soon as possible to at lest 3.0.2 (newest is 3.1.0)
Using occasion and topic - AWS has any plans to move models schema from Draft 04 to something newer?