RESTWS-562 Talk Thread - Adding support for datatypes

[gayanw]

org.openmrs.module.webservices.rest.web.response.ConversionException: patient on class org.openmrs.Encounter

The REST API does not consistently support posting default/full representations as properties of the thing you want to create. To be safe, try replacing all those object (e.g. patient, encounterType, visit, location) with just their uuid. (I think this may have been partially but not completely fixed since I wrote this in 2015, and you can see how some old code I wrote uses just UUIDs instead of the full objects here and here.)

I’ve been working on RESTWS-562. Now for post operations in the swagger doc, full representations will be shown as its model schema. In that case however the example resource would be quite large. See the resource object for creating a Visit: http://jsoneditoronline.org/?id=367e9d5624e93ec563cc32ecae5a99ee

But we can also document with either full representation or default (uuids instead of full objects), depending on the resource if needed. But then I’d need to decide which resources to document with full and which ones to document with default.

What would you recommend?

---