@autobusal/routes-order 1.31.4 → 1.31.5

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 1.31.5
+
+### Added
+
+- **BusTrip carries the pair's AggregateRating** when `/routes/search/facts` reports one (`FactsData.rating`). The aggregate is computed server-side over the same published-review rules the reviews listing uses, and rides the facts cache - the pair page keeps its one-fetch design. Absent rating, the key is not emitted at all.
+
 ## 1.31.4
 
 ### Fixed

package/Facts/types.ts

@@ -17,6 +17,13 @@ export interface FactsData {
   // how many coaches serve the pair in the TIMETABLE, not on a given date
   departures: number
   operators: string[]
+  // Edited: Claude - Date: 2026-08-20
+  // The pair's own review score - the published reviews of every route in
+  // this very timetable, aggregated by obtapi with the same threshold rule
+  // as everything else (null until there is enough to say something honest).
+  // For structured data; note ScheduleRow.rating below is the OPERATOR's
+  // company-wide number, a different thing.
+  rating: { average: number, count: number } | null
   // Two numbers that must never be conflated.
   //
   // `road` is real driving distance from a routing service and is null unless

package/Sections/Schema.tsx

@@ -27,6 +27,19 @@ interface Props {
  * claiming travellers rated this journey when they rated the company. When
  * an operator has no published rating - below the display threshold - it is
  * simply absent, exactly as it is on the page.
+ *
+ * Edited: Claude - Date: 2026-08-20
+ *
+ * The trip now ALSO carries its own AggregateRating - and that is not the
+ * claim the paragraph above forbids, because `facts.rating` is a different
+ * number: obtapi aggregates the published reviews of exactly the routes in
+ * this timetable (Facts::rating, the same set Reviews\BrowseController's
+ * `pair` mode reads), not a company-wide score stretched over one leg.
+ * Travellers who booked these very coaches wrote those reviews, and every
+ * card on the page links to the operator profile where they are read in
+ * full. Below the display threshold obtapi sends null and nothing is
+ * emitted here - an AggregateRating of nothing is a guideline violation,
+ * worse than none.
  */
 const Schema = ({ facts, t }: Props): (JSX.Element | null) => {
   const schedule = facts.schedule ?? [];
@@ -62,6 +75,19 @@ const Schema = ({ facts, t }: Props): (JSX.Element | null) => {
     departureBusStop: { '@type': 'BusStop', name: facts.from },
     arrivalBusStop: { '@type': 'BusStop', name: facts.to },
 
+    // Edited: Claude - Date: 2026-08-20
+    // The pair's own score - see the header comment. Null below the
+    // display threshold, and then the property simply does not exist.
+    ...(facts.rating ? {
+      aggregateRating: {
+        '@type': 'AggregateRating',
+        ratingValue: facts.rating.average,
+        reviewCount: facts.rating.count,
+        bestRating: 5,
+        worstRating: 1
+      }
+    } : {}),
+
     ...(providers.length > 0 ? {
       provider: providers.map(item => organisation(item.name, item.rating))
     } : {}),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@autobusal/routes-order",
-  "version": "1.31.4",
+  "version": "1.31.5",
   "author": "Ferjolt Ozuni",
   "type": "module",
   "main": "index.ts"