Com.Hopper.Hts.Airlines 0.1.18

Summary

• Regenerate the client from the updated OpenAPI spec (model/doc/api changes across AnalyticsApi, CancelForAnyReasonCFARApi, BookingConfirmed, PaymentCard, CreateDgContractExerciseRequest, DgExerciseItinerary, etc.).
• Fix a compile error in ClientUtils.cs where the Api model class collided with the sibling Com.Hopper.Hts.Airlines.Api namespace — Api.TypeEnum/Api.TypeEnumToJsonValue resolved to the namespace. Qualified as Model.Api.* so the type resolves correctly.

⚠️ Breaking changes (source-level, for partners upgrading the NuGet package)

These break compilation when a partner upgrades the client and recompiles. Wire/HTTP behavior remains backwards compatible.

1. AnalyticsApi.PostEventsAsync / PostEventsOrDefaultAsync — parameter order swapped and type changed:

// before
PostEventsAsync(string hCSessionID, Event varEvent, ...)
// after
PostEventsAsync(Event varEvent, Option<string> hCSessionID = default, ...)

Existing calls like PostEventsAsync(sessionId, evt) no longer compile. HC-Session-ID is now optional (for booking_confirmed events). The partial hooks FormatPostEvents, AfterPostEvents, and OnErrorPostEvents also changed signature, so partners who implemented those must update them.

2. CreateDgContractExerciseRequest — itinerary changed from required to optional and the constructor was reordered:

// before
(string contractId, DgExerciseItinerary itinerary, string pnrReference, ...)
// after
(string contractId, string pnrReference, Option<DgExerciseItinerary?> itinerary = default, ...)

Positional construction breaks. The Itinerary property type also changed from DgExerciseItinerary to DgExerciseItinerary? (nullable).

Non-breaking (additive)

• PaymentCard: new optional cardBrand param appended + CardBrand property.
• BookingConfirmed: three new optional params appended (cfarOfferIds, dgOfferIds, bookingReferences).
• AirlineRefundMethod: new enum member ManualCash = 3. (Note: an older client version will throw NotImplementedException if the server returns manual_cash — server-driven, not caused by this diff.)
• Doc/example/comment-only changes elsewhere. Unknown JSON response fields are ignored by the deserializers, so old clients tolerate the new fields.