@v-office/website-sdk 3.5.0 → 3.6.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/cli.mjs CHANGED
@@ -17,7 +17,7 @@ var CLICheckFailed = class extends Error {
17
17
  const toCLIError = (message, cause) => cause instanceof Error ? new CLICheckFailed(`${message}: ${cause.message}`, { cause }) : new CLICheckFailed(message, { cause });
18
18
  //#endregion
19
19
  //#region package.json
20
- var version = "3.5.0";
20
+ var version = "3.6.0";
21
21
  //#endregion
22
22
  //#region src/cli/output.ts
23
23
  const toJson = (value) => Effect.try({
@@ -4,6 +4,7 @@
4
4
 
5
5
  Release notes of `@v-office/website-sdk`, newest first. Each version has its own directory.
6
6
 
7
+ - `versions/3.6.0/CHANGELOG.md`: release notes for 3.6.0
7
8
  - `versions/3.5.0/CHANGELOG.md`: release notes for 3.5.0
8
9
  - `versions/3.4.2/CHANGELOG.md`: release notes for 3.4.2
9
10
  - `versions/3.4.1/CHANGELOG.md`: release notes for 3.4.1
@@ -4,6 +4,7 @@
4
4
 
5
5
  Migration guides of `@v-office/website-sdk`, newest first. Apply them in order when skipping versions.
6
6
 
7
+ - `versions/3.6.0/MIGRATION.md`: Migration: 3.5.0 to 3.6.0
7
8
  - `versions/3.5.0/MIGRATION.md`: Migration: 3.4.2 to 3.5.0
8
9
  - `versions/3.4.2/MIGRATION.md`: Migration: 3.4.1 to 3.4.2
9
10
  - `versions/3.4.1/MIGRATION.md`: Migration: 3.4.0 to 3.4.1
@@ -78,7 +78,7 @@ Sample item:
78
78
  "items": [
79
79
  {
80
80
  "id": "form-response-1",
81
- "author": "Ada Lovelace, stayed in July 2026",
81
+ "author": "Ada L., stayed in July 2026",
82
82
  "rating": "5",
83
83
  "createdAt": "2026-07-10T10:00:00.000Z",
84
84
  "text": "Great stay."
@@ -487,9 +487,9 @@ type RentalReview =
487
487
  };
488
488
  ```
489
489
 
490
- For v10, public answers with the same form-response ID are combined into one review item. Its `rating` is the average of the valid `STARS` answers in that response, and its `text` contains the non-empty `TEXT` answers. Missing public customer data leaves `author` undefined.
490
+ For v10, each review item is one published form response. The PMS names the guest as public pages may show them ("Anna M.") and dates the stay by its month; a review without a known guest has no `author`. Its `rating` is the response's score over the questions the agency counts toward the rental score, and its `text` contains the non-empty `TEXT` answers. `summary.averageRating` is the rental's stored score, the number search shows, so reviews of an agency that counts no question toward the rental score have no `rating` and no summary.
491
491
 
492
- `createdAt` is the form response's creation timestamp, not a travel date. A text-only rental can have `reviews.items` without `reviews.summary`, so check the summary independently. The localized `summary.count` describes form responses with valid ratings and does not necessarily equal `items.length`. It reads `reviews.summary.count.one` for one rating and `reviews.summary.count` otherwise.
492
+ `createdAt` is the form response's creation timestamp, not a travel date. A text-only rental can have `reviews.items` without `reviews.summary`, so check the summary independently. The localized `summary.count` describes the reviews with a rating and does not necessarily equal `items.length`. It reads `reviews.summary.count.one` for one rating and `reviews.summary.count` otherwise.
493
493
 
494
494
  `summary.rating` and `summary.count` are texts for display; their wording and separators change with the locale and the translations. For stars, sorting or structured data, read the numbers next to them on both backends: `averageRating` (the same average as the text, rounded up to one decimal), `maxRating` (`5`) and `ratingCount` (the number in `count`).
495
495
 
@@ -0,0 +1,16 @@
1
+ # Changelog: 3.6.0
2
+
3
+ v10 rental reviews name the guest and the travel month again, and their summary shows the rental
4
+ score search shows.
5
+
6
+ ## Changed
7
+
8
+ - v10 `sdk.static.rentals.getRentals` returns reviews whose `author` reads "Anna M., stayed in
9
+ July 2026" again: the PMS names the guest and dates the stay itself.
10
+ - `reviews.summary.averageRating` is the rental score search shows: published ratings of the
11
+ questions the agency counts toward the rental score, out of 5. `ratingCount` is the
12
+ number of reviews with a rating, and a review's `rating` uses the same questions. If the agency
13
+ counts no question toward the rental score, reviews have no `rating` and the summary is left out.
14
+ - Only reviews the agency published appear.
15
+
16
+ The output shape stays the same. v9 reviews do not change.
@@ -0,0 +1,10 @@
1
+ # Migration: 3.5.0 to 3.6.0
2
+
3
+ ## 1. Upgrade
4
+
5
+ ```sh
6
+ pnpm add @v-office/website-sdk@3.6.0
7
+ ```
8
+
9
+ No changes required. Ratings and the summary now need at least one question the agency counts
10
+ toward the rental score in the PMS; without one, reviews show their text only.
@@ -4,6 +4,7 @@
4
4
 
5
5
  Release notes of `@v-office/website-sdk`, newest first. Each version has its own directory.
6
6
 
7
+ - `versions/3.6.0/CHANGELOG.md`: release notes for 3.6.0
7
8
  - `versions/3.5.0/CHANGELOG.md`: release notes for 3.5.0
8
9
  - `versions/3.4.2/CHANGELOG.md`: release notes for 3.4.2
9
10
  - `versions/3.4.1/CHANGELOG.md`: release notes for 3.4.1
@@ -4,6 +4,7 @@
4
4
 
5
5
  Migration guides of `@v-office/website-sdk`, newest first. Apply them in order when skipping versions.
6
6
 
7
+ - `versions/3.6.0/MIGRATION.md`: Migration: 3.5.0 to 3.6.0
7
8
  - `versions/3.5.0/MIGRATION.md`: Migration: 3.4.2 to 3.5.0
8
9
  - `versions/3.4.2/MIGRATION.md`: Migration: 3.4.1 to 3.4.2
9
10
  - `versions/3.4.1/MIGRATION.md`: Migration: 3.4.0 to 3.4.1
@@ -78,7 +78,7 @@ Sample item:
78
78
  "items": [
79
79
  {
80
80
  "id": "form-response-1",
81
- "author": "Ada Lovelace, stayed in July 2026",
81
+ "author": "Ada L., stayed in July 2026",
82
82
  "rating": "5",
83
83
  "createdAt": "2026-07-10T10:00:00.000Z",
84
84
  "text": "Great stay."
@@ -487,9 +487,9 @@ type RentalReview =
487
487
  };
488
488
  ```
489
489
 
490
- For v10, public answers with the same form-response ID are combined into one review item. Its `rating` is the average of the valid `STARS` answers in that response, and its `text` contains the non-empty `TEXT` answers. Missing public customer data leaves `author` undefined.
490
+ For v10, each review item is one published form response. The PMS names the guest as public pages may show them ("Anna M.") and dates the stay by its month; a review without a known guest has no `author`. Its `rating` is the response's score over the questions the agency counts toward the rental score, and its `text` contains the non-empty `TEXT` answers. `summary.averageRating` is the rental's stored score, the number search shows, so reviews of an agency that counts no question toward the rental score have no `rating` and no summary.
491
491
 
492
- `createdAt` is the form response's creation timestamp, not a travel date. A text-only rental can have `reviews.items` without `reviews.summary`, so check the summary independently. The localized `summary.count` describes form responses with valid ratings and does not necessarily equal `items.length`. It reads `reviews.summary.count.one` for one rating and `reviews.summary.count` otherwise.
492
+ `createdAt` is the form response's creation timestamp, not a travel date. A text-only rental can have `reviews.items` without `reviews.summary`, so check the summary independently. The localized `summary.count` describes the reviews with a rating and does not necessarily equal `items.length`. It reads `reviews.summary.count.one` for one rating and `reviews.summary.count` otherwise.
493
493
 
494
494
  `summary.rating` and `summary.count` are texts for display; their wording and separators change with the locale and the translations. For stars, sorting or structured data, read the numbers next to them on both backends: `averageRating` (the same average as the text, rounded up to one decimal), `maxRating` (`5`) and `ratingCount` (the number in `count`).
495
495
 
@@ -0,0 +1,16 @@
1
+ # Changelog: 3.6.0
2
+
3
+ v10 rental reviews name the guest and the travel month again, and their summary shows the rental
4
+ score search shows.
5
+
6
+ ## Changed
7
+
8
+ - v10 `sdk.static.rentals.getRentals` returns reviews whose `author` reads "Anna M., stayed in
9
+ July 2026" again: the PMS names the guest and dates the stay itself.
10
+ - `reviews.summary.averageRating` is the rental score search shows: published ratings of the
11
+ questions the agency counts toward the rental score, out of 5. `ratingCount` is the
12
+ number of reviews with a rating, and a review's `rating` uses the same questions. If the agency
13
+ counts no question toward the rental score, reviews have no `rating` and the summary is left out.
14
+ - Only reviews the agency published appear.
15
+
16
+ The output shape stays the same. v9 reviews do not change.
@@ -0,0 +1,10 @@
1
+ # Migration: 3.5.0 to 3.6.0
2
+
3
+ ## 1. Upgrade
4
+
5
+ ```sh
6
+ pnpm add @v-office/website-sdk@3.6.0
7
+ ```
8
+
9
+ No changes required. Ratings and the summary now need at least one question the agency counts
10
+ toward the rental score in the PMS; without one, reviews show their text only.
@@ -0,0 +1,3 @@
1
+ {
2
+ "componentsAffectedByHeadlessChange": []
3
+ }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@v-office/website-sdk",
3
- "version": "3.5.0",
3
+ "version": "3.6.0",
4
4
  "description": "Website-facing SDK facade backed by @v-office/sdk-core",
5
5
  "license": "UNLICENSED",
6
6
  "repository": {
@@ -48,7 +48,7 @@
48
48
  },
49
49
  "dependencies": {
50
50
  "@graphql-typed-document-node/core": "3.2.0",
51
- "@v-office/sdk-core": "1.33.0",
51
+ "@v-office/sdk-core": "1.34.0",
52
52
  "effect": "4.0.0-rc.115",
53
53
  "graphql": "17.0.2",
54
54
  "yaml": "^2.9.0"