@v-office/website-sdk 2.4.2 → 2.4.3

package/dist/cli.mjs

@@ -15,7 +15,7 @@ var CLICheckFailed = class extends Error {
 const toCLIError = (message, cause) => cause instanceof Error ? new CLICheckFailed(`${message}: ${cause.message}`, { cause }) : new CLICheckFailed(message, { cause });
 //#endregion
 //#region package.json
-var version = "2.4.2";
+var version = "2.4.3";
 //#endregion
 //#region src/cli/output.ts
 const toJson = (value) => Effect.try({

package/dist/instructions/CHANGELOG.md

@@ -4,6 +4,8 @@ This file is the versioned changelog index for the website SDK instructions.
 
 ## Versions
 
+- `versions/2.4.3/CHANGELOG.md`: `@v-office/website-sdk` 2.4.3 documentation release notes.
+- `versions/2.4.2/CHANGELOG.md`: `@v-office/website-sdk` 2.4.2 release notes.
 - `versions/2.4.0/CHANGELOG.md`: `@v-office/website-sdk` 2.4.0 release notes.
 - `versions/2.3.0/CHANGELOG.md`: `@v-office/website-sdk` 2.3.0 release notes.
 - `versions/2.1.0/CHANGELOG.md`: `@v-office/website-sdk` 2.1.0 release notes.

package/dist/instructions/MIGRATION.md

@@ -4,6 +4,8 @@ This file is the versioned migration index for the website SDK instructions.
 
 ## Available Guides
 
+- `versions/2.4.3/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.4.2 to 2.4.3.
+- `versions/2.4.2/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.4.1 to 2.4.2.
 - `versions/2.4.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.3.x to 2.4.0.
 - `versions/2.3.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.1.0 to 2.3.0.
 - `versions/2.1.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.0.0 to 2.1.0.

package/dist/instructions/README.md

@@ -1,6 +1,6 @@
 # Website SDK Instructions
 
-These instructions describe `@v-office/website-sdk` 2.4.0.
+These instructions describe `@v-office/website-sdk` 2.4.3.
 
 Use this directory as the consumer-facing reference for the package:
 
@@ -15,6 +15,8 @@ Use this directory as the consumer-facing reference for the package:
 - `document-structured-json.md`: `sdk.static.documents.getTermsAndPrivacyPolicy` and structured document JSON rendering rules.
 - `CHANGELOG.md`: versioned changelog index.
 - `MIGRATION.md`: versioned migration index.
+- `versions/2.4.3/`: 2.4.3 documentation release notes and migration guide.
+- `versions/2.4.2/`: 2.4.2 release notes and 2.4.1-to-2.4.2 migration guide.
 - `versions/2.4.0/`: 2.4.0 release notes and 2.3.x-to-2.4.0 migration guide.
 - `versions/2.3.0/`: 2.3.0 release notes and 2.1.0-to-2.3.0 migration guide.
 - `versions/2.1.0/`: 2.1.0 release notes and 2.0.0-to-2.1.0 migration guide.
@@ -63,4 +65,4 @@ website-sdk --backend v9 filters --locale en-US
 website-sdk --backend v10 search --locale de-DE --query "adults=2"
 ```
 
-Config file examples in these docs use the flat `WebsiteSDKConfig` shape introduced in 2.0.0 and kept in 2.4.0.
+Config file examples in these docs use the flat `WebsiteSDKConfig` shape introduced in 2.0.0 and kept in 2.4.3.

package/dist/instructions/versions/2.4.2/CHANGELOG.md

@@ -0,0 +1,30 @@
+# Changelog: 2.4.2
+
+Release date: 2026-07-20
+
+This release adds proposed additional-service quantities and combines related v10 public feedback answers into complete review items.
+
+## Added
+
+- Added optional `proposedQuantity` to additional services for both v9 and v10. The field is returned when the backend supplies a line amount, including `0`.
+- Added the `shouldAddProposedAdditionalServiceAmount` website SDK option. When enabled, proposed quantities greater than zero are selected on the initial quote.
+- Added deterministic pagination for v10 public feedback so rental reviews are not limited to the first backend result page.
+
+## Changed
+
+- Renamed the additional-service field `preSelectedQuantity` to `proposedQuantity`.
+- `shouldAddProposedAdditionalServiceAmount` defaults to `false`, so proposed quantities are informational unless consumers opt in to automatic initial selection.
+- Optional services with a backend amount of `0` can still be returned with their unit charge when the backend provides enough pricing data.
+- v10 public feedback answers with the same form-response ID are now combined into one review item instead of being returned as independent rating-only and text-only items.
+- A combined v10 review uses the form-response ID and creation time, averages valid `STARS` answers, and includes its non-empty `TEXT` answers.
+- v10 review summaries now count form responses with a valid rating rather than individual rating answers.
+
+## Migration Impact
+
+- Replace reads of `additionalService.preSelectedQuantity` with `additionalService.proposedQuantity`.
+- Leave `shouldAddProposedAdditionalServiceAmount` unset or `false` to preserve explicit additional-service selection.
+- Set `shouldAddProposedAdditionalServiceAmount: true` only when the initial quote should include positive backend-proposed quantities.
+- Do not assume each v10 review item represents one feedback answer. It now represents one form response and can contain both `rating` and `text`.
+- Treat a v10 review item's `id` and `createdAt` as form-response metadata.
+- Do not use `reviews.items.length` as the review-summary count.
+- No SDK config-shape or service-call changes are required.

package/dist/instructions/versions/2.4.2/MIGRATION.md

@@ -0,0 +1,94 @@
+# Migration: 2.4.1 to 2.4.2
+
+This guide covers upgrading `@v-office/website-sdk` from 2.4.1 to 2.4.2.
+
+2.4.2 keeps `createWebsiteSDK({ config, options })`, the flat `WebsiteSDKConfig`, and the existing quote and rental service calls. The migration affects additional-service quantities and v10 review grouping.
+
+## Additional Services
+
+### Renamed Quantity
+
+The optional `preSelectedQuantity` field is now named `proposedQuantity`:
+
+```ts
+for (const service of quote.additionalServices) {
+  if (service.proposedQuantity !== undefined) {
+    renderProposedQuantity(service.proposedQuantity);
+  }
+}
+```
+
+The value is the backend-proposed quantity, including `0`. It does not indicate that the service is selected in the quote.
+
+Migration: replace every read of `preSelectedQuantity` with `proposedQuantity` and continue to handle the field as optional.
+
+### Initial Selection
+
+Proposed quantities are not selected by default. To add positive proposed quantities to the initial quote, enable the new website SDK option:
+
+```ts
+const sdk = createWebsiteSDK({
+  config,
+  options: defineWebsiteSDKOptions({
+    shouldAddProposedAdditionalServiceAmount: true,
+  }),
+});
+```
+
+When this option is `true`, the SDK adds each service up to its positive `proposedQuantity` while creating the quote. Normal availability and quantity-limit checks still apply. A proposed quantity of `0` is never selected automatically.
+
+Leave the option unset or set it to `false` when users must explicitly select every optional service.
+
+## v10 Rental Reviews
+
+v10 now combines public answers that have the same form-response ID. One review item can therefore contain both its averaged star rating and its text:
+
+```ts
+const review = {
+  id: "form-response-1",
+  author: "Ada Lovelace, visited in July 2026",
+  rating: "5",
+  createdAt: "2026-07-10T10:00:00.000Z",
+  text: "Great stay.",
+};
+```
+
+For each v10 form response:
+
+- `id` is the form-response ID.
+- `createdAt` is the form-response creation time.
+- `rating` is the average of its valid public `STARS` values.
+- `text` contains its non-empty public `TEXT` answers.
+- `author` remains optional when no public customer information is available.
+- The item is omitted when the response has neither a valid rating nor non-empty text.
+
+If a response contains multiple text answers, they are separated by blank lines and non-empty question titles identify the corresponding text. Review items remain sorted by form-response creation time, newest first.
+
+Rendering should continue to check optional fields independently:
+
+```ts
+for (const rental of await sdk.static.rentals.getRentals({ locale: "de-DE" })) {
+  for (const item of rental.reviews?.items ?? []) {
+    if (item.rating !== undefined) renderReviewRating(item.rating);
+    if (item.text !== undefined) renderReviewText(item.text);
+    renderReviewAuthor(item.author ?? "Anonymous");
+  }
+
+  if (rental.reviews?.summary !== undefined) {
+    renderReviewSummary(rental.reviews.summary);
+  }
+}
+```
+
+The localized `reviews.summary.count` now counts form responses that contain a valid rating. It can differ from both the number of raw answers and `reviews.items.length`. Text-only reviews can still produce `reviews.items` without a summary.
+
+The SDK now fetches all v10 public-feedback pages. Consumers do not need to add pagination logic to `getRentals`.
+
+## Recommended Steps
+
+1. Upgrade to `@v-office/website-sdk` 2.4.2.
+2. Rename `preSelectedQuantity` reads to `proposedQuantity`.
+3. Decide whether backend-proposed quantities should be selected automatically.
+4. Expect one v10 review item per usable form response rather than one item per answer.
+5. Keep presence checks for review `rating`, `text`, `author`, and `summary`.
+6. Smoke-test quotes with absent, zero, and positive proposed quantities and rentals with rating-only, text-only, and combined feedback.

package/dist/instructions/versions/2.4.3/CHANGELOG.md

@@ -0,0 +1,14 @@
+# Changelog: 2.4.3
+
+Release date: 2026-07-20
+
+This release adds the instructions that were missing from the 2.4.2 package.
+
+## Added
+
+- Added the missing 2.4.2 changelog and migration instructions for proposed additional-service quantities and grouped v10 reviews.
+
+## Migration Impact
+
+- No runtime behavior or public API changes are introduced relative to 2.4.2.
+- Consumers upgrading from 2.4.1 or earlier should follow `versions/2.4.2/MIGRATION.md`.

package/dist/instructions/versions/2.4.3/MIGRATION.md

@@ -0,0 +1,5 @@
+# Migration: 2.4.2 to 2.4.3
+
+The 2.4.2 package was missing its release instructions. Version 2.4.3 adds those instructions without changing runtime behavior or the public API.
+
+No migration is required from 2.4.2. If upgrading from 2.4.1 or earlier, follow `versions/2.4.2/MIGRATION.md`.

package/instructions/CHANGELOG.md

@@ -4,6 +4,8 @@ This file is the versioned changelog index for the website SDK instructions.
 
 ## Versions
 
+- `versions/2.4.3/CHANGELOG.md`: `@v-office/website-sdk` 2.4.3 documentation release notes.
+- `versions/2.4.2/CHANGELOG.md`: `@v-office/website-sdk` 2.4.2 release notes.
 - `versions/2.4.0/CHANGELOG.md`: `@v-office/website-sdk` 2.4.0 release notes.
 - `versions/2.3.0/CHANGELOG.md`: `@v-office/website-sdk` 2.3.0 release notes.
 - `versions/2.1.0/CHANGELOG.md`: `@v-office/website-sdk` 2.1.0 release notes.

package/instructions/MIGRATION.md

@@ -4,6 +4,8 @@ This file is the versioned migration index for the website SDK instructions.
 
 ## Available Guides
 
+- `versions/2.4.3/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.4.2 to 2.4.3.
+- `versions/2.4.2/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.4.1 to 2.4.2.
 - `versions/2.4.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.3.x to 2.4.0.
 - `versions/2.3.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.1.0 to 2.3.0.
 - `versions/2.1.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.0.0 to 2.1.0.

package/instructions/README.md

@@ -1,6 +1,6 @@
 # Website SDK Instructions
 
-These instructions describe `@v-office/website-sdk` 2.4.0.
+These instructions describe `@v-office/website-sdk` 2.4.3.
 
 Use this directory as the consumer-facing reference for the package:
 
@@ -15,6 +15,8 @@ Use this directory as the consumer-facing reference for the package:
 - `document-structured-json.md`: `sdk.static.documents.getTermsAndPrivacyPolicy` and structured document JSON rendering rules.
 - `CHANGELOG.md`: versioned changelog index.
 - `MIGRATION.md`: versioned migration index.
+- `versions/2.4.3/`: 2.4.3 documentation release notes and migration guide.
+- `versions/2.4.2/`: 2.4.2 release notes and 2.4.1-to-2.4.2 migration guide.
 - `versions/2.4.0/`: 2.4.0 release notes and 2.3.x-to-2.4.0 migration guide.
 - `versions/2.3.0/`: 2.3.0 release notes and 2.1.0-to-2.3.0 migration guide.
 - `versions/2.1.0/`: 2.1.0 release notes and 2.0.0-to-2.1.0 migration guide.
@@ -63,4 +65,4 @@ website-sdk --backend v9 filters --locale en-US
 website-sdk --backend v10 search --locale de-DE --query "adults=2"
 ```
 
-Config file examples in these docs use the flat `WebsiteSDKConfig` shape introduced in 2.0.0 and kept in 2.4.0.
+Config file examples in these docs use the flat `WebsiteSDKConfig` shape introduced in 2.0.0 and kept in 2.4.3.

package/instructions/versions/2.4.2/CHANGELOG.md

@@ -0,0 +1,30 @@
+# Changelog: 2.4.2
+
+Release date: 2026-07-20
+
+This release adds proposed additional-service quantities and combines related v10 public feedback answers into complete review items.
+
+## Added
+
+- Added optional `proposedQuantity` to additional services for both v9 and v10. The field is returned when the backend supplies a line amount, including `0`.
+- Added the `shouldAddProposedAdditionalServiceAmount` website SDK option. When enabled, proposed quantities greater than zero are selected on the initial quote.
+- Added deterministic pagination for v10 public feedback so rental reviews are not limited to the first backend result page.
+
+## Changed
+
+- Renamed the additional-service field `preSelectedQuantity` to `proposedQuantity`.
+- `shouldAddProposedAdditionalServiceAmount` defaults to `false`, so proposed quantities are informational unless consumers opt in to automatic initial selection.
+- Optional services with a backend amount of `0` can still be returned with their unit charge when the backend provides enough pricing data.
+- v10 public feedback answers with the same form-response ID are now combined into one review item instead of being returned as independent rating-only and text-only items.
+- A combined v10 review uses the form-response ID and creation time, averages valid `STARS` answers, and includes its non-empty `TEXT` answers.
+- v10 review summaries now count form responses with a valid rating rather than individual rating answers.
+
+## Migration Impact
+
+- Replace reads of `additionalService.preSelectedQuantity` with `additionalService.proposedQuantity`.
+- Leave `shouldAddProposedAdditionalServiceAmount` unset or `false` to preserve explicit additional-service selection.
+- Set `shouldAddProposedAdditionalServiceAmount: true` only when the initial quote should include positive backend-proposed quantities.
+- Do not assume each v10 review item represents one feedback answer. It now represents one form response and can contain both `rating` and `text`.
+- Treat a v10 review item's `id` and `createdAt` as form-response metadata.
+- Do not use `reviews.items.length` as the review-summary count.
+- No SDK config-shape or service-call changes are required.

package/instructions/versions/2.4.2/MIGRATION.md

@@ -0,0 +1,94 @@
+# Migration: 2.4.1 to 2.4.2
+
+This guide covers upgrading `@v-office/website-sdk` from 2.4.1 to 2.4.2.
+
+2.4.2 keeps `createWebsiteSDK({ config, options })`, the flat `WebsiteSDKConfig`, and the existing quote and rental service calls. The migration affects additional-service quantities and v10 review grouping.
+
+## Additional Services
+
+### Renamed Quantity
+
+The optional `preSelectedQuantity` field is now named `proposedQuantity`:
+
+```ts
+for (const service of quote.additionalServices) {
+  if (service.proposedQuantity !== undefined) {
+    renderProposedQuantity(service.proposedQuantity);
+  }
+}
+```
+
+The value is the backend-proposed quantity, including `0`. It does not indicate that the service is selected in the quote.
+
+Migration: replace every read of `preSelectedQuantity` with `proposedQuantity` and continue to handle the field as optional.
+
+### Initial Selection
+
+Proposed quantities are not selected by default. To add positive proposed quantities to the initial quote, enable the new website SDK option:
+
+```ts
+const sdk = createWebsiteSDK({
+  config,
+  options: defineWebsiteSDKOptions({
+    shouldAddProposedAdditionalServiceAmount: true,
+  }),
+});
+```
+
+When this option is `true`, the SDK adds each service up to its positive `proposedQuantity` while creating the quote. Normal availability and quantity-limit checks still apply. A proposed quantity of `0` is never selected automatically.
+
+Leave the option unset or set it to `false` when users must explicitly select every optional service.
+
+## v10 Rental Reviews
+
+v10 now combines public answers that have the same form-response ID. One review item can therefore contain both its averaged star rating and its text:
+
+```ts
+const review = {
+  id: "form-response-1",
+  author: "Ada Lovelace, visited in July 2026",
+  rating: "5",
+  createdAt: "2026-07-10T10:00:00.000Z",
+  text: "Great stay.",
+};
+```
+
+For each v10 form response:
+
+- `id` is the form-response ID.
+- `createdAt` is the form-response creation time.
+- `rating` is the average of its valid public `STARS` values.
+- `text` contains its non-empty public `TEXT` answers.
+- `author` remains optional when no public customer information is available.
+- The item is omitted when the response has neither a valid rating nor non-empty text.
+
+If a response contains multiple text answers, they are separated by blank lines and non-empty question titles identify the corresponding text. Review items remain sorted by form-response creation time, newest first.
+
+Rendering should continue to check optional fields independently:
+
+```ts
+for (const rental of await sdk.static.rentals.getRentals({ locale: "de-DE" })) {
+  for (const item of rental.reviews?.items ?? []) {
+    if (item.rating !== undefined) renderReviewRating(item.rating);
+    if (item.text !== undefined) renderReviewText(item.text);
+    renderReviewAuthor(item.author ?? "Anonymous");
+  }
+
+  if (rental.reviews?.summary !== undefined) {
+    renderReviewSummary(rental.reviews.summary);
+  }
+}
+```
+
+The localized `reviews.summary.count` now counts form responses that contain a valid rating. It can differ from both the number of raw answers and `reviews.items.length`. Text-only reviews can still produce `reviews.items` without a summary.
+
+The SDK now fetches all v10 public-feedback pages. Consumers do not need to add pagination logic to `getRentals`.
+
+## Recommended Steps
+
+1. Upgrade to `@v-office/website-sdk` 2.4.2.
+2. Rename `preSelectedQuantity` reads to `proposedQuantity`.
+3. Decide whether backend-proposed quantities should be selected automatically.
+4. Expect one v10 review item per usable form response rather than one item per answer.
+5. Keep presence checks for review `rating`, `text`, `author`, and `summary`.
+6. Smoke-test quotes with absent, zero, and positive proposed quantities and rentals with rating-only, text-only, and combined feedback.

package/instructions/versions/2.4.3/CHANGELOG.md

@@ -0,0 +1,14 @@
+# Changelog: 2.4.3
+
+Release date: 2026-07-20
+
+This release adds the instructions that were missing from the 2.4.2 package.
+
+## Added
+
+- Added the missing 2.4.2 changelog and migration instructions for proposed additional-service quantities and grouped v10 reviews.
+
+## Migration Impact
+
+- No runtime behavior or public API changes are introduced relative to 2.4.2.
+- Consumers upgrading from 2.4.1 or earlier should follow `versions/2.4.2/MIGRATION.md`.

package/instructions/versions/2.4.3/MIGRATION.md

@@ -0,0 +1,5 @@
+# Migration: 2.4.2 to 2.4.3
+
+The 2.4.2 package was missing its release instructions. Version 2.4.3 adds those instructions without changing runtime behavior or the public API.
+
+No migration is required from 2.4.2. If upgrading from 2.4.1 or earlier, follow `versions/2.4.2/MIGRATION.md`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@v-office/website-sdk",
-  "version": "2.4.2",
+  "version": "2.4.3",
   "description": "Website-facing SDK facade backed by @v-office/sdk-core",
   "bin": {
     "website-sdk": "./dist/cli.mjs"
@@ -41,7 +41,7 @@
   },
   "dependencies": {
     "@graphql-typed-document-node/core": "3.2.0",
-    "@v-office/sdk-core": "^1.5.2",
+    "@v-office/sdk-core": "^1.5.3",
     "effect": "4.0.0-beta.85",
     "graphql": "16.14.2",
     "yaml": "^2.9.0"