@voyant-travel/connect-flights 0.1.0

package/README.md

@@ -0,0 +1,38 @@
+# @voyant-travel/connect-flights
+
+Voyant Connect flights adapter. Implements the Voyant `FlightConnectorAdapter`
+contract by proxying to a Voyant Connect deployment's connect-api over HTTP
+(via [`@voyant-travel/connect-sdk`](../connect-sdk)).
+
+A Voyant deployment swaps its in-process demo flight adapter for this to route
+flights through Voyant Connect to the real GDS connector behind a connection
+(e.g. HiSky): search, price, book/hold, list orders, issue tickets, and cancel.
+
+## Usage
+
+```ts
+import { createConnectFlightAdapter } from "@voyant-travel/connect-flights";
+
+const adapter = createConnectFlightAdapter({
+  connect: {
+    apiKey: process.env.VOYANT_CONNECT_API_KEY!,
+    operatorId: process.env.VOYANT_OPERATOR_ID!,
+    baseUrl: process.env.VOYANT_CONNECT_BASE_URL, // defaults to the hosted API
+  },
+});
+
+// In the deployment's flights runtime:
+//   resolveAdapter(c) => adapter   (connectionId is supplied per request via ctx)
+```
+
+The connection id targeted by each call comes from `ctx.connectionId`.
+
+## Scope
+
+Implements the flight order lifecycle: `searchFlights`, `priceOffer`,
+`bookFlight`, `getOrder`, `cancelOrder`, `listOrders`, `ticketOrder`.
+
+Seat maps and ancillaries are not proxied yet: the connector contract models
+them per-offer (pre-book), whereas the connect-sdk client exposes them
+per-order (post-book), so they need an explicit mapping rather than a
+pass-through. Tracked as a follow-up.

package/dist/index.d.ts

@@ -0,0 +1,45 @@
+/**
+ * Voyant Connect flights adapter.
+ *
+ * Implements the Voyant `FlightConnectorAdapter` contract by proxying to a
+ * Voyant Connect deployment's connect-api over HTTP (via `@voyant-travel/
+ * connect-sdk`). A deployment swaps its in-process demo adapter for this to
+ * route flights through Voyant Connect to the real GDS connector behind a
+ * connection (e.g. HiSky) — book/hold, list, ticket, and cancel orders.
+ *
+ * Flights speak one contract end-to-end (connect-api ↔ hosted connector ↔
+ * deployment all use `@voyant-travel/flights-contracts`), and connect-api
+ * returns those contract shapes verbatim under its `{ data }` envelope (which
+ * the connect-sdk transport unwraps). The connect-sdk client types flight
+ * payloads opaquely as `JsonObject`, so this adapter is a thin, typed
+ * pass-through: forward the contract request, return the contract response.
+ *
+ * The connection id is taken from `ctx.connectionId` on every call — the
+ * deployment supplies which connection each request targets.
+ */
+import { type VoyantConnectClient, type VoyantConnectClientOptions } from "@voyant-travel/connect-sdk";
+import type { FlightAdapterCapabilities, FlightConnectorAdapter } from "@voyant-travel/flights-contracts/contract/adapter";
+export interface ConnectFlightAdapterOptions {
+    /** A pre-built Voyant Connect client. */
+    client?: VoyantConnectClient;
+    /** Options to build a client (apiKey, operatorId, baseUrl) when `client` is not supplied. */
+    connect?: VoyantConnectClientOptions;
+    /** `capabilities.provider` label — default `"connect"`. */
+    provider?: string;
+    /**
+     * Declared flight capabilities for connections behind this adapter. The
+     * authoritative capabilities live per-connection at connect-api (from the
+     * connector's manifest); this static value is a best-effort hint for the
+     * deployment's orchestration. Defaults to holds + list-orders (Voyant
+     * Connect always lists orders from its own store, even when the underlying
+     * GDS connector cannot enumerate them).
+     */
+    capabilities?: FlightAdapterCapabilities;
+}
+/**
+ * Build a `FlightConnectorAdapter` backed by Voyant Connect. Drop the result
+ * into the deployment's flights runtime `resolveAdapter` in place of the demo
+ * adapter.
+ */
+export declare function createConnectFlightAdapter(options: ConnectFlightAdapterOptions): FlightConnectorAdapter;
+//# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;GAkBG;AAEH,OAAO,EAML,KAAK,mBAAmB,EACxB,KAAK,0BAA0B,EAChC,MAAM,4BAA4B,CAAC;AACpC,OAAO,KAAK,EACV,yBAAyB,EAGzB,sBAAsB,EAKvB,MAAM,mDAAmD,CAAC;AAE3D,MAAM,WAAW,2BAA2B;IAC1C,yCAAyC;IACzC,MAAM,CAAC,EAAE,mBAAmB,CAAC;IAC7B,6FAA6F;IAC7F,OAAO,CAAC,EAAE,0BAA0B,CAAC;IACrC,2DAA2D;IAC3D,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB;;;;;;;OAOG;IACH,YAAY,CAAC,EAAE,yBAAyB,CAAC;CAC1C;AAYD;;;;GAIG;AACH,wBAAgB,0BAA0B,CACxC,OAAO,EAAE,2BAA2B,GACnC,sBAAsB,CAsExB"}

package/dist/index.js

@@ -0,0 +1,75 @@
+/**
+ * Voyant Connect flights adapter.
+ *
+ * Implements the Voyant `FlightConnectorAdapter` contract by proxying to a
+ * Voyant Connect deployment's connect-api over HTTP (via `@voyant-travel/
+ * connect-sdk`). A deployment swaps its in-process demo adapter for this to
+ * route flights through Voyant Connect to the real GDS connector behind a
+ * connection (e.g. HiSky) — book/hold, list, ticket, and cancel orders.
+ *
+ * Flights speak one contract end-to-end (connect-api ↔ hosted connector ↔
+ * deployment all use `@voyant-travel/flights-contracts`), and connect-api
+ * returns those contract shapes verbatim under its `{ data }` envelope (which
+ * the connect-sdk transport unwraps). The connect-sdk client types flight
+ * payloads opaquely as `JsonObject`, so this adapter is a thin, typed
+ * pass-through: forward the contract request, return the contract response.
+ *
+ * The connection id is taken from `ctx.connectionId` on every call — the
+ * deployment supplies which connection each request targets.
+ */
+import { createVoyantConnectClient, } from "@voyant-travel/connect-sdk";
+function resolveClient(options) {
+    if (options.client)
+        return options.client;
+    if (!options.connect) {
+        throw new Error("createConnectFlightAdapter requires either a `client` or `connect` option");
+    }
+    return createVoyantConnectClient(options.connect);
+}
+/**
+ * Build a `FlightConnectorAdapter` backed by Voyant Connect. Drop the result
+ * into the deployment's flights runtime `resolveAdapter` in place of the demo
+ * adapter.
+ */
+export function createConnectFlightAdapter(options) {
+    const client = resolveClient(options);
+    const capabilities = options.capabilities ?? {
+        provider: options.provider ?? "connect",
+        declared: ["flight/holds", "flight/list-orders"],
+    };
+    return {
+        capabilities,
+        async searchFlights(ctx, request) {
+            return (await client.flights.searchOnConnection(ctx.connectionId, request));
+        },
+        async priceOffer(ctx, request) {
+            return (await client.flights.price(ctx.connectionId, request));
+        },
+        async bookFlight(ctx, request) {
+            return (await client.flights.book(ctx.connectionId, request));
+        },
+        async getOrder(ctx, orderId) {
+            return (await client.flights.getOrder(ctx.connectionId, orderId));
+        },
+        // connect-api's cancel route takes no reason body, so it is not forwarded.
+        async cancelOrder(ctx, orderId) {
+            return (await client.flights.cancelOrder(ctx.connectionId, orderId));
+        },
+        // Reads connect-api's operator-scoped order store — GDS connectors can't
+        // enumerate orders, so this does not depend on adapter list support.
+        async listOrders(ctx, query) {
+            const clientQuery = {
+                ...(query.cursor ? { cursor: query.cursor } : {}),
+                ...(query.limit !== undefined ? { limit: query.limit } : {}),
+                ...(query.search ? { q: query.search } : {}),
+                ...(query.status ? { status: query.status } : {}),
+            };
+            return (await client.flights.listOrders(ctx.connectionId, clientQuery));
+        },
+        // Promote a held order to ticketed (connect-api gates on the connector's
+        // `flight/holds` capability).
+        async ticketOrder(ctx, orderId) {
+            return (await client.flights.ticketOrder(ctx.connectionId, orderId));
+        },
+    };
+}

package/package.json

@@ -0,0 +1,70 @@
+{
+  "name": "@voyant-travel/connect-flights",
+  "version": "0.1.0",
+  "description": "Voyant Connect flights adapter for Voyant deployments.",
+  "license": "Apache-2.0",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/voyant-travel/connect.git",
+    "directory": "packages/connect-flights"
+  },
+  "homepage": "https://github.com/voyant-travel/connect#readme",
+  "bugs": {
+    "url": "https://github.com/voyant-travel/connect/issues"
+  },
+  "type": "module",
+  "main": "./dist/index.js",
+  "types": "./src/index.ts",
+  "sideEffects": false,
+  "keywords": [
+    "voyant",
+    "voyant-connect",
+    "flights",
+    "adapter",
+    "sdk",
+    "typescript"
+  ],
+  "exports": {
+    ".": {
+      "types": "./src/index.ts",
+      "default": "./dist/index.js"
+    }
+  },
+  "files": [
+    "dist"
+  ],
+  "scripts": {
+    "build": "tsc -p tsconfig.json",
+    "lint": "eslint src --max-warnings 0",
+    "check-types": "tsc --noEmit"
+  },
+  "dependencies": {
+    "@voyant-travel/connect-sdk": "workspace:*"
+  },
+  "peerDependencies": {
+    "@voyant-travel/flights-contracts": ">=0.104.6 <1"
+  },
+  "peerDependenciesMeta": {
+    "@voyant-travel/flights-contracts": {
+      "optional": true
+    }
+  },
+  "devDependencies": {
+    "@voyant-sdk/eslint-config": "workspace:*",
+    "@voyant-sdk/typescript-config": "workspace:*",
+    "@voyant-travel/flights-contracts": "^0.104.6",
+    "eslint": "^9.39.1",
+    "typescript": "5.9.2"
+  },
+  "publishConfig": {
+    "access": "public",
+    "main": "./dist/index.js",
+    "types": "./dist/index.d.ts",
+    "exports": {
+      ".": {
+        "types": "./dist/index.d.ts",
+        "import": "./dist/index.js"
+      }
+    }
+  }
+}