The problem is the spec is just invalid. The Comments model just doesn’t follow the supported spec.
--
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 swagger-swaggers...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
So I don’t really know what you’re trying to describe but if you change the Comment definition to just
"Comment": {
"type": "object",
"title": "Comment",
"required": [
"id"
],
"properties": {
"id": {
"title": "id",
"type": "string"
}
}
}
it will render as expected.
Keep in mind, ‘null’ is not a valid type, nor is an array of types.
--
Glad to hear you got it sorted out. Swagger on!
From: <swagger-sw...@googlegroups.com> on behalf of Andrew Campbell <andrew....@synchronoss.com>
Reply-To: "swagger-sw...@googlegroups.com" <swagger-sw...@googlegroups.com>
Date: Thursday, 18 August 2016 at 02:25
To: Swagger <swagger-sw...@googlegroups.com>
Subject: Re: <!-- invalid XML --> in Swagger UI Example Value
Thank you!
The problem was the missing "type": "string". This was further obfuscated by a typo in the full 13k line spec; I wouldn't have found either of those problems without your help.
--