steve-donovan

enums for Contact.DeviceType and Document.DocumentType

9

Fixes #199 ## Changes for this pull request Contact has deviceType as String; Document has documentType as String. Unfriendly to API consumer, as noted by remark in discord channel.

## Description FlightOrder currently defines deviceType and documentType as String, they should really be enums for friendlier API I noticed someone in discord with the issue. as per spec ```...

Should return an empty array, empty list, or optional, instead of NULL

2

## Description As an example, the _FlightOfferSearch_ class has an array representing _Stops_ within a _Segment_. If there are no stops, the array is NULL and can cause an NPE...

## Description paymentType missing, and other properties with wrong types ``` "HotelProduct_PolicyDetails": { "title": "HotelProduct_PolicyDetails", "description": "Booking Rules", "type": "object", "properties": { "paymentType": { "$ref": "#/definitions/PaymentType" }, "guarantee": { "$ref":...

shopping hotel-offers : issue sending array of hotel id's

3

## Description API indicates that it is possible to supply an array of hotel id's, but the Params class used by API only works with Strings. Passing an array causes...

## Description HotelBookings only offers 2 methods, both JSON based, whereas FlightOrders offers a more friendly and convenient set of methods. ``` public FlightOrder post(JsonObject body) throws ResponseException { public...