@autobusal/routes-order 1.37.4 → 1.37.6

package/Sections/Sections.tsx

@@ -1,10 +1,14 @@
 import { TFunction } from 'i18next';
 import Facts from '../Facts/Facts';
 import Faq from '../Faq/Faq';
+import Availability from '../Availability/Availability';
+import AvailabilitySchema from '../Availability/Schema';
 import Schedule from '../Schedule/Schedule';
 import Links from '../Links/Links';
 import Schema from './Schema';
 import { useGetFacts } from '../Facts/services';
+import { useGetAvailability } from '../Availability/services';
+import { prepare } from '../Availability/service';
 import buildQuestions from '../Facts/questions';
 import { stopped } from '../Facts/service';
 import { Nav, Anchor, Anchored } from './styles';
@@ -17,6 +21,7 @@ interface Props {
 
 const TRIPS = 'trips';
 const FACTS = 'facts';
+const AVAILABILITY = 'availability';
 const SCHEDULE = 'schedule';
 const FAQ = 'faq';
 const LINKS = 'links';
@@ -36,12 +41,25 @@ const LINKS = 'links';
  * response, and letting each fetch its own would have doubled what the
  * prerender crawl costs on every pair in the sitemap.
  *
+ * Edited: Claude - Date: 2026-09-16
+ *
+ * TWO fetches now, and the second one is not a regression of the paragraph
+ * above. The next-30-days section needs live seat counts, and the facts
+ * payload is cached for six hours precisely because nothing in it moves -
+ * folding one into the other would either publish stale seat counts or
+ * throw away a cache that every pair page depends on. It stays one request
+ * per page rather than one per departure, and it renders NOTHING when it
+ * fails, so a page whose second call never answers is exactly the page it
+ * was yesterday.
+ *
  * The nav renders only when there is more than the wizard to navigate to -
  * a bar whose only link is "Trips" is furniture.
  */
 const Sections = ({ from, to, t }: Props): (JSX.Element | null) => {
   const { data } = useGetFacts(from, to);
 
+  const { data: dates } = useGetAvailability(from, to);
+
   const facts = data?.facts;
 
   const links = data?.links ?? { from: [], to: [], reverse: null };
@@ -66,6 +84,19 @@ const Sections = ({ from, to, t }: Props): (JSX.Element | null) => {
   // that happen to agree today.
   const questions = buildQuestions(facts, t);
 
+  /**
+   * Edited: Claude - Date: 2026-09-16
+   *
+   * Prepared once, here, and handed to the section AND to its structured
+   * data - the same arrangement `questions` above is in, for the same
+   * reason. Null when the endpoint did not answer, answered with nothing,
+   * or answered with a window in which no coach runs; every consumer below
+   * is gated on that single value, so there is no arrangement in which the
+   * nav offers a link to a section that rendered nothing, or the markup
+   * describes departures the page does not list.
+   */
+  const availability = prepare(dates, t);
+
   /**
    * Edited: Claude - Date: 2026-08-21
    *
@@ -108,6 +139,10 @@ const Sections = ({ from, to, t }: Props): (JSX.Element | null) => {
         <Anchor href={ `#${ TRIPS }` }>{ t('routes_order.sections.trips') }</Anchor>
         <Anchor href={ `#${ FACTS }` }>{ t('routes_order.sections.facts') }</Anchor>
 
+        { availability && (
+          <Anchor href={ `#${ AVAILABILITY }` }>{ t('routes_order.sections.availability') }</Anchor>
+        ) }
+
         { schedule.length > 0 && (
           <Anchor href={ `#${ SCHEDULE }` }>{ t('routes_order.sections.schedule') }</Anchor>
         ) }
@@ -122,12 +157,34 @@ const Sections = ({ from, to, t }: Props): (JSX.Element | null) => {
            show - same facts, same numbers, same operators. */ }
       <Schema facts={ facts } questions={ questions } t={ t } />
 
+      { /* Edited: Claude - Date: 2026-09-16
+           One BusTrip per dated departure, alongside the pair-level one
+           above rather than instead of it: that one describes the journey,
+           these describe the actual coaches on actual days. Built from the
+           same prepared array the section renders. */ }
+      { availability && <AvailabilitySchema data={ availability } t={ t } /> }
+
       <Anchored>
         <Facts id={ FACTS } facts={ facts } t={ t } />
       </Anchored>
 
       { dead && onward }
 
+      { /* Edited: Claude - Date: 2026-09-16
+           ABOVE the timetable, because a reader who has a date in mind is
+           answered here and a reader who does not is answered below. The
+           timetable is the pattern - what runs, in the abstract; this is
+           the next thirty days of it, with fares and seats. Renders nothing
+           at all when the endpoint gives us nothing, which is also what
+           happens on a pair that has stopped running: the notice in the
+           facts block above has already said so, and thirty rows of "no
+           departures" underneath it would be a wall, not an answer. */ }
+      { availability && (
+        <Anchored>
+          <Availability id={ AVAILABILITY } data={ availability } t={ t } />
+        </Anchored>
+      ) }
+
       <Anchored>
         <Schedule id={ SCHEDULE } from={ facts.from } to={ facts.to } rows={ schedule } t={ t } />
       </Anchored>

package/package.json

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