@autobusal/routes-order 1.31.1 → 1.31.3

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 1.31.3
+
+### Fixed
+
+- **The results page's facts/schedule block now renders on the very first screen**, not only once a date has been picked. `/bus-lines/:from/:to` - the dateless URL the sitemap lists and the prerender crawl snapshots - was always on step 1, so `<Sections>` (price/duration/departures + the per-route schedule table + the pair's JSON-LD) never mounted for a single search engine or non-JS crawler. It now also renders on step 1; the bare `/bus-lines` search form (no pair in the URL) is unaffected since it has nothing to fetch.
+
+## 1.31.2
+
+### Changed
+
+- **The route card and booking summary show the operator's `display_name`**, not `company` - an operator that set a brand name (`@autobusal/providers` 1.34.0) now appears under that name in search results and the booking summary, same as everywhere else it's now shown.
+
 ## 1.31.1
 
 ### Changed

package/Found/Route/Route.tsx

@@ -131,7 +131,7 @@ const Route = ({ data, type, date, passengers, t, onSave, children }: Props): JS
 
       <Trip>
         <Company>
-          <LinkCompany to={ bookOnUrl ?? data.operator.link } target="_blank" rel="noopener noreferrer" title={ data.operator.company }><img src={ data.operator.logo_url || LOGO_FALLBACK } onError={ (e) => { e.currentTarget.onerror = null; e.currentTarget.src = LOGO_FALLBACK; } } alt={ data.operator.company } /></LinkCompany>
+          <LinkCompany to={ bookOnUrl ?? data.operator.link } target="_blank" rel="noopener noreferrer" title={ data.operator.display_name }><img src={ data.operator.logo_url || LOGO_FALLBACK } onError={ (e) => { e.currentTarget.onerror = null; e.currentTarget.src = LOGO_FALLBACK; } } alt={ data.operator.display_name } /></LinkCompany>
 
           { /* Edited: Ferjolt Ozuni - Date: 2026-08-03
                The OPERATOR's rating rather than this route's: a single route
@@ -240,7 +240,7 @@ const Route = ({ data, type, date, passengers, t, onSave, children }: Props): JS
             text={
               <>
                 <RiBus2Line />
-                { isExternalRedirect ? t('routes_order.step2.route.book_on', { provider: data.operator.company }) : t('routes_order.step2.route.select') }
+                { isExternalRedirect ? t('routes_order.step2.route.book_on', { provider: data.operator.display_name }) : t('routes_order.step2.route.select') }
               </>
             }
             onClick={ () => (isExternalRedirect && bookOnUrl ? window.open(bookOnUrl, '_blank', 'noopener,noreferrer') : onSave(data)) }

package/RoutesOrder.tsx

@@ -317,16 +317,26 @@ const RoutesOrder = ({ t }: Props): JSX.Element => {
         />
       ) }
 
-      { /* Edited: Ferjolt Ozuni - Date: 2026-08-03
-           Roadmap Tier 3.2. Only on the route-choosing screens, and only
-           once the URL names a real pair: this is the page a search engine
-           lands on, and it is the one place the block adds anything. Past
-           step 2 the reader has picked a coach and is filling in passenger
-           details - facts about the pair are noise at that point.
-
-           It renders nothing at all for a pair with no facts, so a page that
-           would only have gained an empty box does not gain a box. */ }
-      { (showStep2 || showStep3) && (
+      { /* Edited: Ferjolt Ozuni - Date: 2026-08-03, widened 2026-08-11
+           Roadmap Tier 3.2. NOT gated on step2/step3 (as it was originally)
+           - it now also renders on showStep1, which is what actually matters:
+           /bus-lines/:from/:to is the URL the sitemap lists and the
+           prerender crawl snapshots, and that URL is ALWAYS on step 1 - a
+           date has not been picked yet, so step2/step3 never mount and the
+           block never rendered for a single crawler. A logged human visitor
+           benefits the same way a search engine does: price/duration/
+           schedule for the pair, visible before they commit to a date.
+
+           Bare /bus-lines (no :from/:to) leaves both props undefined,
+           useGetFacts short-circuits on that, and Sections' own guard
+           returns null with nothing fetched - so the generic search form
+           gains no empty box underneath it.
+
+           Past step 2 the reader has picked a coach and is filling in
+           passenger details - facts about the pair are noise at that point,
+           which is why it still stops at step 3 and does not follow onto
+           checkout. */ }
+      { (showStep1 || showStep2 || showStep3) && (
         <Sections
           from={ fromCity?.slug ?? params.from }
           to={ toCity?.slug ?? params.to }

package/Step5/Summary/About/About.tsx

@@ -65,10 +65,10 @@ const About = ({ type, step1, data, number, t }: Props): (JSX.Element | null) =>
                rather than as the operator being identified. */ }
           <Carrier>
             { data.operator.logo_url && (
-              <Logo src={ data.operator.logo_url } alt={ data.operator.company } />
+              <Logo src={ data.operator.logo_url } alt={ data.operator.display_name } />
             ) }
 
-            <Operator>{ data.operator.company }</Operator>
+            <Operator>{ data.operator.display_name }</Operator>
           </Carrier>
 
           <Leg>

package/package.json

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