Question
Last activity: 19 Apr 2016 0:58 EDT
We are facing issue while generating model schema and model for our work object using the OOTB swagger js, please read description for more info
We discovered a bug in the swagger js, where for some complex structures, the model schema generated shows the embedded objects as null even though we populate data. There was an SR opened ( SR-A13508), but closed by Engineering.
This seems to only show up on the large complex claim. Even if we do create the right structures, the landing page will not render all the information.
The API definition loaded into Swagger
"modifer":{
"type":"array",
"items":{
"type":"string"
}
},
How Swagger renders the information under Model
modifier(Array[modifier,optional),
How Swagger renders the information on the Landing Page under Model Schema
"modifier":[
null
]
Message was edited by: Lochan to add Category
Hi Shatan,
Just to add on here, this was the resolution stated in the SR.
This is an issue with third party tool used by PRPC. Swagger UI is a third party technology that we are using to develop PegaAPI documentation. Please refer to http://editor.swagger.io that allows to trial and error with swagger UI.
Pega version: Pega 7.1.8
Additionally: the issue is raised for 7.2 version and internally swagger js is updated and tested hence issue not reproduced. They will spin off new SR for the latest version after checking with the engineering team.
We welcome thoughts form other members of the community!
Regards,
Lochan | Online Community Moderator | Pegasystems Inc.
The SR was there and it was resolved, earlier the version PRPC interacting was, an older version of swagger, it was updated to a correct version in the newer version of PRPC, but we were still facing the issue, Carl had asked us to raise a query here so that it would be easy for him to track his conversation with the engg team.
Pegasystems Inc.
CA
Hi Shantan, if you have discovered a bug in Swagger, I suggest you report this on Swagger forums here: http://swagger.io/forum/. We only ship Swagger with Pega because it is used internally for our Pega API documentation. We do not own the support or maintenance of Swagger.