aves-sdk 1.8.0 → 2.0.0

package/CHANGELOG.md

@@ -5,6 +5,49 @@ All notable changes to this project are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.0.0] - 2026-08-05
+
+### Changed
+
+- **Breaking:** flat operation aliases were removed; use namespaced domain clients only.
+- **Breaking:** enum-typed fields now reject arbitrary strings at compile time.
+- **Breaking:** `AvesError.status` retains AVES casing and `AvesError.code` is `number | undefined`.
+- **Breaking:** master-record responses reflect the actual API payload, including server-only fields; `dynamicFields` is an array.
+- Fixed AVES language codes (`01` Italian, `02` English), raw warning text preservation, and the `PaymentDetail` `@PaumentNote` wire spelling.
+
+### Migration
+
+| Change | Symptom on upgrade | Fix |
+| ------ | ------------------ | --- |
+| Flat aliases removed | Runtime `TypeError` | Insert the domain namespace: `client.search` → `client.master.search` |
+| Enum types narrowed | Compile errors for enum fields receiving `string` | Use exported enum objects or unions |
+| `AvesError.status` casing | `err.status === "error"` no longer matches | Compare with `RsStatusValue` (`"OK"`, `"ERROR"`, `"WARNING"`, `"TIMEOUT"`) |
+| `AvesError.code` | Absent codes are `undefined`, not `0` | Check for `undefined` |
+| `MasterRecordDetailResponse` corrected | Type gains server-only fields | Remove local re-declarations |
+| `dynamicFields` is an array | Single-object assignment fails | Wrap the field in an array |
+
+---
+
+## [1.9.0] - 2026-08-03
+
+### Changed
+
+- **Breaking:** `upsertRecord` spreads `masterRecordDetail` into `data` — `result.data.recordCode`
+- **Breaking:** booking create/mod/status spreads `bookingFileDetail` into `data` — `result.data.bookingFileCode`
+- **Breaking:** `getPackageDetail` spreads `packageDetail` into `data` — `result.data.pCode`
+- **Breaking:** response `*List` fields are flat Detail arrays (no inner `*Detail` wrapper) — e.g. `data.packageList?.[0]`, `data.masterRecordList`, `data.bookingFileList`, `data.bookedServiceList`
+- **Breaking:** nested booking/catalog lists unwrapped the same way (`passengerList`, `serviceList`, `paxPriceList`, …)
+- Input aliases: `customerRecordCode` ↔ `customerDetail`; `bookingFileStatus` / `fileStatus` as string or `{ value }`; `paxAssociated: string[]`; mod `selectedPackageList` ↔ `selectedPackageDetail`
+
+### Added
+
+- Response helpers: `listDetailApiSchema`, `flattenResponseDetail`, `createFlattenedResponseSchema`, `createListResponseSchema`
+- Request helpers: `createApiSchema`, `valueFieldSchema`, `coalesceCustomerRecordCode`, `coalesceListHead`, `coalesceWireAliases`
+- Shared primitives: `LanguageCodeSchema`, `StringishSchema`, `DateRangeSchema`, `StatusOnlyResponseSchema`, `createWireSchemaPair`
+- `yarn typecheck` script (`tsc --noEmit`)
+
+---
+
 ## [1.8.0] - 2026-08-03
 
 ### Added

package/README.md

@@ -27,7 +27,7 @@ const client = new AvesClient({
   timeoutMs: 30_000, // optional
 });
 
-const result = await client.search({
+const result = await client.master.search({
   searchType: 'CODE',
   recordCode: '508558',
 });
@@ -41,20 +41,17 @@ if (result.success) {
 
 ## Client shape
 
-`AvesClient` is a facade over domain clients. **Prefer namespaces.** Flat methods are auto-bound from domain prototypes (no hand-maintained forwarders).
+`AvesClient` is a facade over domain clients. Operations are namespaced by domain.
 
 ```typescript
-// canonical
 await client.booking.createBooking(params);
 await client.packages.searchPackages(params);
 await client.master.search({ searchType: 'CODE', recordCode: '508558' });
-
-// flat compat (same implementations)
-await client.createBooking(params);
-await client.searchPackages(params);
-await client.search({ searchType: 'CODE', recordCode: '508558' });
 ```
 
+Migration from 1.x: insert the appropriate domain namespace (for example,
+`client.search` → `client.master.search`). See the [2.0.0 migration notes](./CHANGELOG.md).
+
 | Namespace | Methods |
 | --------- | ------- |
 | `master` | `search`, `upsertRecord` |
@@ -105,7 +102,7 @@ type Result<T, E> =
 
 ## Master records
 
-### `search(params)` / `client.master.search`
+### `client.master.search(params)`
 
 | `searchType` | Required fields |
 | ------------ | --------------- |
@@ -124,18 +121,18 @@ const byCode = await client.master.search({
   recordCode: '508558',
 });
 
-const byEmail = await client.search({
+const byEmail = await client.master.search({
   searchType: 'EMAIL',
   email: 'user@example.com',
 });
 ```
 
-### `upsertRecord(record)` / `client.master.upsertRecord`
+### `client.master.upsertRecord(record)`
 
 `insertCriteria`: `'S'` always insert · `'N'` skip if exists · `'T'` update all (default) · `'M'` secondary fields only.
 
 ```typescript
-const result = await client.upsertRecord({
+const result = await client.master.upsertRecord({
   name: 'Jane Smith',
   email: 'jane@example.com',
   languageCode: '02',
@@ -143,7 +140,7 @@ const result = await client.upsertRecord({
 });
 
 if (result.success) {
-  console.log(result.data.masterRecordDetail?.recordCode);
+  console.log(result.data.recordCode);
 }
 ```
 
@@ -168,8 +165,8 @@ if (result.success) {
 
 ```typescript
 const created = await client.booking.createBooking({
-  customerDetail: { recordCode: '138311' },
-  bookingFileStatus: { value: 'QUOTATION' },
+  customerRecordCode: '138311', // or customerDetail: { recordCode: '138311' }
+  bookingFileStatus: 'QUOTATION', // or { value: 'QUOTATION', expiredDate? }
   startDate: '2015-01-22T00:00:00',
   endDate: '2015-01-25T00:00:00',
   selectedServiceList: [
@@ -182,7 +179,7 @@ const created = await client.booking.createBooking({
       endDate: '2015-01-25T00:00:00',
       qty: '1',
       pax: '2',
-      paxAssociated: [],
+      paxAssociated: [], // or string[] like ['001','002']
       avesSession: '1',
     },
   ],
@@ -198,7 +195,8 @@ const created = await client.booking.createBooking({
 });
 
 if (created.success) {
-  console.log(created.data.bookingFileDetail?.bookingFileCode);
+  console.log(created.data.bookingFileCode);
+  console.log(created.data.bookedServiceList?.[0]?.serviceStatus);
 }
 ```
 
@@ -273,7 +271,7 @@ await client.booking.modBookingHeader({
 await client.booking.setBookingStatus({
   customerRecordCode: '000170',
   bookingFileCode: '14/000081',
-  fileStatus: { value: 'CANCELED' },
+  fileStatus: 'CANCELED', // or { value: 'CANCELED' }
 });
 
 await client.booking.setBookingServiceStatus({
@@ -340,6 +338,9 @@ const detail = await client.packages.getPackageDetail({
 });
 
 await client.packages.commitPackage({ packageCode: '14/PACKAGE001' });
+
+if (packages.success) console.log(packages.data.packageList?.[0]?.pCode);
+if (detail.success) console.log(detail.data.pCode, detail.data.serviceList?.[0]);
 ```
 
 ---
@@ -349,7 +350,7 @@ await client.packages.commitPackage({ packageCode: '14/PACKAGE001' });
 ```typescript
 import { AvesClient, AvesError } from 'aves-sdk';
 
-const result = await client.search({
+const result = await client.master.search({
   searchType: 'CODE',
   recordCode: '508558',
 });
@@ -375,9 +376,11 @@ You do not handle XML attribute prefixes yourself. Attr vs element is decided by
 One outbound path for all ops:
 
 1. Valibot validates camelCase input  
-2. `createApiSchema(schema, shape, wrap?)` → `toWireBody` (optional list wrap + empty `paxAssociated` normalize + `camelToPascalKeys`)  
+2. `createApiSchema(schema, shape, wrap?)` → `toWireBody` (optional list wrap + `paxAssociated` string[]/empty normalize + `camelToPascalKeys`)  
 3. `AvesTransport.invokeOp` adds `RqHeader`, optional `bodyKey` nest, POSTs XML  
 
+Inbound: `createResponseSchema` / `createFlattenedResponseSchema` / `createListResponseSchema` → camelCase + optional detail spread or typed list RS; `listDetailApiSchema` unwraps wire `*List`/`*Detail` to flat arrays; `coalesceWireAliases` normalizes dialect attrs. Input aliases: `valueFieldSchema`, `coalesceCustomerRecordCode`, `coalesceListHead`. Shared primitives: `LanguageCodeSchema`, `StringishSchema`, `DateRangeSchema`, `StatusOnlyResponseSchema`.
+
 Element-only roots use `elementOnlyWire` (`{}`). Master upsert nests under `bodyKey: "MasterRecordDetail"`; master search and booking spread fields at the RQ root.
 
 ### Request shapes (one family per op)
@@ -407,18 +410,19 @@ Editing CreateBooking shapes does not affect SearchFile or AvesSearch.
 | `MasterRecordsClient` | search / upsert |
 | `BookingClient` | booking file ops + search practices |
 | `PackageCatalogClient` | package/program catalog |
-| `client/types.ts` | `AvesClientDeps` / `AvesClientFlat` |
-| `client/flat-aliases.ts` | bind flat compat methods from domain prototypes |
+| `client/types.ts` | `AvesClientDeps` |
 | `src/xml/` | XML root helpers + JSON ↔ XML |
 
-Flat aliases (`client.createBooking`, …) are attached in the constructor — add a domain method once and both surfaces work.
-
 Outbound path: validate → `createApiSchema` / `toWireBody` → `invokeOp` → XML POST.
 
 ---
 
 ## Types
 
+Operations are available only through `client.master`, `client.booking`, and
+`client.packages`; flat aliases were removed in 2.0.0. See the
+[migration notes](./CHANGELOG.md) when upgrading.
+
 ```typescript
 import type {
   AvesClientOptions,