@v-office/website-sdk 2.0.0 → 2.1.1

package/instructions/search.md

@@ -6,9 +6,9 @@ Use the live search API to search rentals with a URL query-string style input:
 
 ```ts
 const result = await sdk.live.search.search({
-  locale: 'de-DE',
-  query: 'start=01-07-2026&end=08-07-2026&adults=2&wifi=true',
-})
+  locale: "de-DE",
+  query: "start=01-07-2026&end=08-07-2026&adults=2&wifi=true",
+});
 ```
 
 The service is implemented for both `v9` and `v10` backends and returns normalized rental result items. Filtering by `rentalIdsIn` is currently implemented for `v10` only.
@@ -17,12 +17,13 @@ The service is implemented for both `v9` and `v10` backends and returns normaliz
 
 ```ts
 type RentalSearchInput = {
-  locale: 'de-DE' | 'en-US'
-  query: string
-  rentalIdsIn?: readonly string[]
-  limit?: number
-  cursor?: string
-}
+  locale: "de-DE" | "en-US";
+  query: string;
+  rentalIdsIn?: readonly string[];
+  voucher?: string;
+  limit?: number;
+  cursor?: string;
+};
 ```
 
 Sample:
@@ -32,6 +33,7 @@ Sample:
   "locale": "de-DE",
   "query": "start=01-07-2026&end=08-07-2026&adults=2&children=1&wifi=true",
   "rentalIdsIn": ["123", "456"],
+  "voucher": "SUMMER26",
   "limit": 20
 }
 ```
@@ -49,7 +51,7 @@ The `query` field is a URL query-string style value without a leading `?`.
 Use `&` to combine period, occupancy, and filter parameters:
 
 ```ts
-'start=20-06-2026&end=27-06-2026&adults=2&wifi'
+"start=20-06-2026&end=27-06-2026&adults=2&wifi";
 ```
 
 ### Period Queries
@@ -59,25 +61,25 @@ Use one supported period structure per query.
 Exact period search:
 
 ```ts
-'start=20-06-2026&end=27-06-2026'
+"start=20-06-2026&end=27-06-2026";
 ```
 
 Flexible search by month:
 
 ```ts
-'month=06-2026&nights=7'
-'month=06-2026&month=07-2026&nights=7'
-'month=06-2026&weekend'
-'month=06-2026&month=07-2026&weekend'
+"month=06-2026&nights=7";
+"month=06-2026&month=07-2026&nights=7";
+"month=06-2026&weekend";
+"month=06-2026&month=07-2026&weekend";
 ```
 
 Flexible search by exact date tuples:
 
 ```ts
-'dates=20-06-2026,22-06-2026&nights=2'
-'dates=20-06-2026,22-06-2026&dates=04-07-2026,11-07-2026&nights=2'
-'dates=20-06-2026,22-06-2026&weekend'
-'dates=20-06-2026,22-06-2026&dates=04-07-2026,11-07-2026&weekend'
+"dates=20-06-2026,22-06-2026&nights=2";
+"dates=20-06-2026,22-06-2026&dates=04-07-2026,11-07-2026&nights=2";
+"dates=20-06-2026,22-06-2026&weekend";
+"dates=20-06-2026,22-06-2026&dates=04-07-2026,11-07-2026&weekend";
 ```
 
 ### Occupancy And Filters
@@ -85,16 +87,16 @@ Flexible search by exact date tuples:
 Append occupancy and filter parameters with `&`:
 
 ```ts
-'start=20-06-2026&end=27-06-2026&adults=2'
-'start=20-06-2026&end=27-06-2026&adults=2&childrenAges=5%2C13&babies=1&pets=1'
-'start=20-06-2026&end=27-06-2026&adults=2&wifi'
+"start=20-06-2026&end=27-06-2026&adults=2";
+"start=20-06-2026&end=27-06-2026&adults=2&childrenAges=5%2C13&babies=1&pets=1";
+"start=20-06-2026&end=27-06-2026&adults=2&wifi";
 ```
 
 Boolean filters can be provided as presence-only flags when supported:
 
 ```ts
-'wifi'
-'wifi&bbq=true'
+"wifi";
+"wifi&bbq=true";
 ```
 
 ### Invalid Combinations
@@ -102,27 +104,29 @@ Boolean filters can be provided as presence-only flags when supported:
 Do not mix exact period search with flexible period options:
 
 ```ts
-'start=20-06-2026&end=27-06-2026&nights=7'
-'start=20-06-2026&end=27-06-2026&weekend'
+"start=20-06-2026&end=27-06-2026&nights=7";
+"start=20-06-2026&end=27-06-2026&weekend";
 ```
 
 Do not mix `month` and `dates` in the same flexible query:
 
 ```ts
-'month=06-2026&dates=20-06-2026,22-06-2026&nights=2'
+"month=06-2026&dates=20-06-2026,22-06-2026&nights=2";
 ```
 
 Flexible queries require either `nights` or `weekend`, but not both:
 
 ```ts
-'month=06-2026'
-'dates=20-06-2026,22-06-2026'
-'month=06-2026&nights=7&weekend'
+"month=06-2026";
+"dates=20-06-2026,22-06-2026";
+"month=06-2026&nights=7&weekend";
 ```
 
 Dates should use `DD-MM-YYYY`; months should use `MM-YYYY`.
 
 Use `rentalIdsIn` to restrict results to specific rental IDs. This option is currently supported by `v10` only.
+Use `voucher` to price v10 search results with a voucher code. This option is currently supported by `v10` only.
+For v10, `pets` is a mapped BooleanFilter exposed by `getFilters` and maps to one pet; use `petsCount` for an exact count and do not send both keys in one query.
 
 `limit` defaults to `20`. Treat `cursor` as opaque and pass back `pageInfo.nextCursor` unchanged.
 
@@ -209,10 +213,11 @@ website-sdk --backend v10 search --locale de-DE --query "adults=2" --limit 10
 website-sdk --backend v10 search --locale de-DE --query "adults=2" --limit 10 --cursor "10"
 ```
 
-Restrict results to specific rental IDs with `--rental-ids-in` (`v10` only):
+Restrict results to specific rental IDs or price with a voucher code (`v10` only):
 
 ```sh
 website-sdk --backend v10 search --locale de-DE --query "adults=2" --rental-ids-in "123,456"
+website-sdk --backend v10 search --locale de-DE --query "adults=2" --voucher SUMMER26
 ```
 
 Use files instead of environment variables:

package/instructions/versions/2.0.0/MIGRATION.md

@@ -25,7 +25,7 @@ Legacy 1.x-style API:
 ## Package Import
 
 ```ts
-import { createWebsiteSDK, defineWebsiteSDKOptions } from '@v-office/website-sdk'
+import { createWebsiteSDK, defineWebsiteSDKOptions } from "@v-office/website-sdk";
 ```
 
 The new package still exports `defineCMSSDKOptions` as an alias for `defineWebsiteSDKOptions`, but new code should use the Website naming.
@@ -35,41 +35,41 @@ The new package still exports `defineCMSSDKOptions` as an alias for `defineWebsi
 Before:
 
 ```ts
-import { createCMSSDKFromParsedConfig, defineCMSSDKOptions } from '@v-office/website-sdk'
+import { createCMSSDKFromParsedConfig, defineCMSSDKOptions } from "@v-office/website-sdk";
 
 const sdk = createCMSSDKFromParsedConfig({
-  backend: 'v10',
+  backend: "v10",
   v10: {
-    apiEndpoint: 'https://api.example.com/graphql',
-    accessToken: '...',
-    imageBaseUrl: 'https://images.example.com',
+    apiEndpoint: "https://api.example.com/graphql",
+    accessToken: "...",
+    imageBaseUrl: "https://images.example.com",
   },
   options: defineCMSSDKOptions({
     rentalScope: {
-      propertyId: 'property-1',
+      propertyId: "property-1",
     },
   }),
-})
+});
 ```
 
 After:
 
 ```ts
-import { createWebsiteSDK, defineWebsiteSDKOptions } from '@v-office/website-sdk'
+import { createWebsiteSDK, defineWebsiteSDKOptions } from "@v-office/website-sdk";
 
 const sdk = createWebsiteSDK({
   config: {
-    backend: 'v10',
-    apiEndpoint: 'https://api.example.com/graphql',
-    accessToken: '...',
-    imageBaseUrl: 'https://images.example.com',
+    backend: "v10",
+    apiEndpoint: "https://api.example.com/graphql",
+    accessToken: "...",
+    imageBaseUrl: "https://images.example.com",
   },
   options: defineWebsiteSDKOptions({
     rentalScope: {
-      propertyId: 'property-1',
+      propertyId: "property-1",
     },
   }),
-})
+});
 ```
 
 ## Config Shape
@@ -123,7 +123,7 @@ Several legacy domain aliases remain exported, including `BookingInput`, `Bookin
 Legacy errors exposed `CMSError` with a `backend` field:
 
 ```ts
-if (error instanceof CMSError && error.backend === 'v9') {
+if (error instanceof CMSError && error.backend === "v9") {
   // legacy handling
 }
 ```
@@ -132,7 +132,7 @@ if (error instanceof CMSError && error.backend === 'v9') {
 
 ```ts
 if (error instanceof CoreSDKError) {
-  console.error(error.source, error.operation, error.message)
+  console.error(error.source, error.operation, error.message);
 }
 ```
 

package/instructions/versions/2.1.0/CHANGELOG.md

@@ -0,0 +1,32 @@
+# Changelog: 2.1.0
+
+Release date: 2026-07-08
+
+This release extends the 2.0.0 website SDK facade without changing the flat config shape or main SDK construction API.
+
+## Added
+
+- Added v10 legal document access through `sdk.static.documents.getTermsAndPrivacyPolicy({ locale })` and `getTermsAndPrivacyPolicyEffect`.
+- Added `document-structured-json.md` instructions for legal document output and structured document rendering.
+- Added v10 contact submission through `messengeremail_newContactRequest`, with shared validation for v9 and v10 contact requests.
+- Added `validateContactSubmitInput`, `ContactSubmitValidationIssue`, and `ContactSubmitValidationIssueCode` exports.
+- Added v10 search voucher pricing via `SearchSearchInput.voucher` and CLI `--voucher`.
+- Added `quote.voucher` metadata for quoted voucher status.
+- Added v10 mapped `pets` search filter, exposed by `static.filter.getFilters` as a localized BooleanFilter.
+- Added backend-specific website SDK facade types such as `WebsiteSDKV9`, `WebsiteSDKV10`, `WebsiteSDKV10Static`, and `WebsiteSDKV10Live`.
+
+## Changed
+
+- v10 quote multi-rate handling now marks unavailable additional services and cancellation policies with `available: false` and `unavailableReason`.
+- Quote selection errors can now include `UnavailableQuoteCombination` when a selected add-on/policy combination cannot be priced.
+- Booking card sections now use a stable display order so included lines, selected add-ons, taxes, modifiers, and fallback sections render predictably.
+- Contact validation now rejects blank required fields, invalid email addresses, invalid country codes, and overly long values before backend submission.
+- v9 contact submission now uses the same core contact input and validation path as v10.
+
+## Migration Impact
+
+- No config migration is required from 2.0.0.
+- Existing search calls continue to work; use `voucher` only for v10 voucher pricing and use either `pets` or `petsCount`, not both.
+- Existing quote rendering should tolerate the new optional `voucher`, `available`, and `unavailableReason` fields.
+- Existing quote selection error handling should add a fallback for `UnavailableQuoteCombination`.
+- Existing contact forms should surface `CoreSDKError` validation issues from `error.cause.issues`.

package/instructions/versions/2.1.0/MIGRATION.md

@@ -0,0 +1,89 @@
+# Migration: 2.0.0 to 2.1.0
+
+This guide covers upgrading `@v-office/website-sdk` from 2.0.0 to 2.1.0.
+
+2.1.0 is a minor release. Keep using `createWebsiteSDK({ config, options })`, the flat `WebsiteSDKConfig`, and separate `WebsiteSDKOptions`.
+
+## What To Review
+
+### Documents
+
+v10 SDK instances now expose:
+
+```ts
+const documents = await sdk.static.documents.getTermsAndPrivacyPolicy({ locale: "de-DE" });
+```
+
+The output may contain `terms` and/or `privacyPolicy`, each with `{ subject, data }`. `data` is the published document revision data as a string. If your app renders this data, see `../../document-structured-json.md`.
+
+This API is v10-only. Code that handles both backends should narrow by `sdk.backend === "v10"` before calling `sdk.static.documents`.
+
+### Contact
+
+Contact requests are validated before submission on both v9 and v10. Validation failures reject with `CoreSDKError` using `operation: "contact.submit.validation"` and field details in `error.cause.issues`.
+
+Required fields are `title`, `surname`, `email`, `subject`, and `message`. Validation also checks email format, two-letter uppercase country codes, and maximum field lengths.
+
+Migration: update contact forms to display field-level validation issues instead of treating every contact error as a backend failure.
+
+### Search
+
+`SearchSearchInput` now accepts `voucher?: string` for v10 pricing:
+
+```ts
+await sdk.live.search.search({
+  locale: "de-DE",
+  query: "adults=2",
+  voucher: "SUMMER26",
+});
+```
+
+The CLI equivalent is `--voucher SUMMER26`.
+
+v10 filters now expose a mapped BooleanFilter with `searchParameterQueryKey: "pets"` and localized labels (`Dogs welcome` / `Hunde willkommen`). It maps to one pet in occupancy. Use either `pets` or `petsCount`, not both.
+
+### Quote
+
+Available quotes can include:
+
+```ts
+quote.voucher; // { code, status, message? }
+```
+
+`status` is `"applied"`, `"not_applied"`, or `"unknown"`. v10 can detect applied voucher modifiers; v9 uses `"unknown"` for available voucher quotes.
+
+Additional services and cancellation policies may now include:
+
+```ts
+{
+  available: false,
+  unavailableReason: "..."
+}
+```
+
+Migration: disable unavailable options in the UI and keep handling unknown optional fields gracefully.
+
+Quote selection errors can now include `UnavailableQuoteCombination` when a selected add-on/cancellation-policy combination cannot be priced. Add a generic message for unsupported combinations.
+
+### Public Types
+
+The root package now exports backend-specific facade types:
+
+- `WebsiteSDKV9`
+- `WebsiteSDKV10`
+- `WebsiteSDKSharedStatic`
+- `WebsiteSDKSharedLive`
+- `WebsiteSDKV10Static`
+- `WebsiteSDKV10Live`
+
+Use these only when you need backend-specific narrowing. Existing `WebsiteSDK` imports remain valid.
+
+## Recommended Steps
+
+1. Upgrade to `@v-office/website-sdk` 2.1.0.
+2. Update contact form error handling for `error.cause.issues`.
+3. If you render quotes, support optional `quote.voucher`, `available`, and `unavailableReason`.
+4. Add handling for `UnavailableQuoteCombination` in quote selection failures.
+5. If you use v10 search filters, render the new `pets` BooleanFilter and avoid combining it with `petsCount`.
+6. Use `sdk.static.documents.getTermsAndPrivacyPolicy` for v10 terms/privacy output where needed.
+7. Run a focused smoke test for search, quote selection, booking, contact submission, and v10 documents.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@v-office/website-sdk",
-  "version": "2.0.0",
+  "version": "2.1.1",
   "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.0.0",
+    "@v-office/sdk-core": "^1.2.1",
     "effect": "4.0.0-beta.85",
     "graphql": "16.14.2",
     "yaml": "^2.9.0"
@@ -65,12 +65,13 @@
     "cli": "node --env-file=.env dist/cli.mjs",
     "build": "tsdown",
     "codegen:v9:graphql": "graphql-codegen --config codegen/v9/graphql-codegen/codegen.ts",
+    "codegen": "pnpm run codegen:v9:graphql",
     "dev": "tsdown --watch",
     "typecheck": "tsc --noEmit",
     "lint": "oxlint .",
     "lint:fix": "oxlint --fix .",
     "fmt": "oxfmt",
     "fmt:check": "oxfmt --check",
-    "check": "pnpm run typecheck && pnpm run lint && pnpm run fmt:check"
+    "check": "pnpm run typecheck && pnpm run lint"
   }
 }