I'm trying to debug a strange situation where there is an intermittent
absence of properties from a single definition in the swagger spec
generated in a Java service. When I say intermittent, I mean that whenever
I start my service, there is a chance that there are no properties in that
particular definition; this is causing our compatibility tests (which use
Swagger spec to detect potentially breaking changes) to frequently fail.
For example if I were to expect a definition like:
"ExampleClass":{
"allOf":[
{"$ref":"#/definitions/ParentClass"},
{
"type":"object",
"properties":{
"key1":{"type":"string"},
"key2":{"type":"string"},
"key3":{"type":"string"}
}
}
]
}
Sometimes, we would get:
"ExampleClass":{
"allOf":[
{"$ref":"#/definitions/ParentClass"},
{
"type":"object",
"properties":{}
}
]
}
Does anyone have any ideas on why this might be happening? For some reason this
seems to be the only class that has this issue, out of over 100 other
definitions generated...And I can't seem to find a difference between the
classes that work and this one that does not.
--
You received this message because you are subscribed to the Google Groups
"Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
