@autobusal/operator-routes 1.10.5 → 1.11.0

package/Locations/Browse/Browse.tsx

@@ -19,10 +19,14 @@ const Browse = ({ routeId, data, t, onReload }: Props): JSX.Element => {
     );
   }
 
-  const items = data.map(item => (
+  const items = data.map((item, index) => (
     <Item
       key={ item.id }
       item={ item }
+      /* which end of the journey this is - nobody arrives at the stop they
+         board at, and nobody departs the one they get off at */
+      isFirst={ index === 0 }
+      isLast={ index === data.length - 1 }
       routeId={ routeId }
       t={ t }
       onReload={ onReload }

package/Locations/Browse/Item.tsx

@@ -13,11 +13,13 @@ import Withdraw from '../Withdraw/Withdraw';
 interface Props {
   routeId: number
   item: LocationData
+  isFirst: boolean
+  isLast: boolean
   t: TFunction<'normal'>
   onReload: () => void
 }
 
-const Item = ({ routeId, item, t, onReload }: Props): JSX.Element => {
+const Item = ({ routeId, item, isFirst, isLast, t, onReload }: Props): JSX.Element => {
   const { register, handleSubmit, formState: { errors } } = useForm<LocationForm>();
 
   const { mutate: Save, isPending: isPendingUpdate } = usePostUpdate(routeId, item.id);
@@ -97,18 +99,41 @@ const Item = ({ routeId, item, t, onReload }: Props): JSX.Element => {
             </select>
           </div>
 
+          { /*
+               Claude - 2026-08-30 (asked for by Ferjolt): ARRIVAL FIRST, then
+               departure - that is the order the coach does them in, and the
+               order a timetable is read in. It was the other way round.
+
+               And each end of the journey has only one meaningful time:
+               nobody arrives at the stop they board at, nobody departs the
+               one they get off at. Those are shown as not applicable rather
+               than demanded; the server mirrors the meaningful one into the
+               column so everything that reads both still works.
+             */ }
           <div className="row">
-            { t('locations_manage.city.departure', { ns: 'common' }) }
+            { t('locations_manage.city.arrival', { ns: 'common' }) }
 
-            <input type="text" defaultValue={ item.departure } { ...register('departure', Validate('required', t)) } />
-            { Display(errors.departure) }
+            { isFirst ? (
+              <input type="text" disabled value="" placeholder={ t('locations_manage.city.not_applicable', { ns: 'common' }) } />
+            ) : (
+              <>
+                <input type="text" defaultValue={ item.arrival } { ...register('arrival', Validate('required', t)) } />
+                { Display(errors.arrival) }
+              </>
+            ) }
           </div>
 
           <div className="row">
-            { t('locations_manage.city.arrival', { ns: 'common' }) }
+            { t('locations_manage.city.departure', { ns: 'common' }) }
 
-            <input type="text" defaultValue={ item.arrival } { ...register('arrival', Validate('required', t)) } />
-            { Display(errors.arrival) }
+            { isLast ? (
+              <input type="text" disabled value="" placeholder={ t('locations_manage.city.not_applicable', { ns: 'common' }) } />
+            ) : (
+              <>
+                <input type="text" defaultValue={ item.departure } { ...register('departure', Validate('required', t)) } />
+                { Display(errors.departure) }
+              </>
+            ) }
           </div>
         </Data>
 

package/package.json

@@ -1,7 +1,10 @@
 {
   "name": "@autobusal/operator-routes",
-  "version": "1.10.5",
+  "version": "1.11.0",
   "author": "Ferjolt Ozuni",
   "type": "module",
-  "main": "index.ts"
+  "main": "index.ts",
+  "publishConfig": {
+    "access": "public"
+  }
 }

package/CHANGELOG.md

@@ -1,109 +0,0 @@
-# Changelog
-
-## 1.10.1 - 2026-08-30
-
-- Staged dynamic pricing (roadmap P5): a per-route screen for the price rules - the opt-in, the operator's own caps, and the rules as a NUMBERED list read top to bottom, because the first rule whose band matches is the only one that applies. Each row says what it will actually do once the cap has had its say.
-
-## 1.10.0 (2026-08-29)
-
-- Editors offer Save & Close alongside Save & Stay, so correcting a record no longer bounces you back to its list every time (opt-in per page, editing only).
-
-## 1.9.0 (2026-08-29)
-
-- Route schedules and unavailability periods can be planned five years ahead, not one - the picker's ceiling was the only limit.
-- The 'add a stop' picker is searchable: every station on the platform was one native select, so finding your own city meant scrolling hundreds of options in an order nothing sorted for you.
-
-## 1.6.1
-
-### Fixed
-
-- **A copied or reversed route could not be opened.** The manage page read `data.drivers.registered` with the optional chain stopping one level short, so a route whose `drivers` relation was null crashed the whole page. Guarded. (Platform audit RT-09e; the backend now also copies the drivers row.)
-
-## 1.6.0
-
-### Added
-
-- **The stops taken off a route can be put back.** Withdrawal never destroyed
-  anything - the stop's row, its price rows and the fares on them all survive
-  - and both the API endpoint and this package's `useRestoreLocation` hook
-  had existed since it shipped. Nothing rendered them: the locations response
-  filters on `active`, so a withdrawn stop was never mentioned and no screen
-  could offer to bring one back. From the operator's side a withdrawal was
-  invisible and permanent, which is the one thing it was built not to be.
-  The section appears only when the route has something to restore.
-
-## 1.5.2
-
-### Removed
-
-- **The confirm dialog in front of removing a stop.** It asked the question
-  the withdrawal panel already asks - the panel names the stop, lists
-  everybody still travelling through it and has its own button - and it
-  answered one part wrongly, warning that the fares would have to be entered
-  again. That stopped being true when calibration began reconciling price
-  rows instead of rebuilding them: measured on a ten-stop route, withdrawing
-  a stop keeps fourteen of sixteen fares and drops only the two legs through
-  the stop itself.
-
-## 1.3.3
-
-### Fixed
-
-- **The ticket-language dropdown offered a country code and three options.**
-  It listed the two content languages plus Greek as `gr` - the code for the
-  country; the language is `el` - so an operator choosing it got English
-  tickets and no error to say so. Now all fifteen languages the API can
-  print, under their own names and their real codes.
-
-## 1.3.2
-
-### Added
-
-- **A stop added in a multi-zone country says so.** Times are stored local
-  to their stop, and a country with no zone recorded falls back to the
-  application's clock - a duration that reads plausibly and is wrong by
-  hours. The API now answers `warning: 'timezone'` and the operator is told,
-  because the operator is who sees the wrong number and would otherwise
-  "fix" it by editing times that are correct as stored.
-
-### Fixed
-
-- **`useAddLocation` returns its response.** It was awaited and discarded,
-  so `onSuccess` received undefined - harmless while the endpoint answered
-  with an empty object, and it would have swallowed the warning above.
-
-## [1.3.1] - 2026-08-07
-
-### Fixed
-
-- **Transiting country select no longer defaults to Afghanistan.** `value`
-  was `0`, so submitting without touching the field added the first country
-  in the list to the route's transit list.
-
-## 1.3.0
-
-**The operator's own notice windows.**
-
-- `information_en|sq` replaces `policies_en|sq` on the route form.
-- Two new fields: cancellation notice and reschedule notice, in hours before departure, with a note saying the two things an operator cannot guess from the labels — that **empty means "not offered on this line"** (not zero, which would be offering it right up until the coach pulls away), and that these numbers are **never shown to passengers**.
-
-They decide whether Flexible Ticket may be sold on the line and what window it grants. A passenger only ever sees the resolved consequence.
-
-All notable changes to this package are documented here. This project follows [Keep a Changelog](https://keepachangelog.com/) and [Semantic Versioning](https://semver.org/).
-
-## [1.2.0] - 2026-07-25
-
-### Added
-
-- **"Required Passenger Details" checkbox list on the route form** (sex /
-  passport / phone / WhatsApp / Telegram), stored as
-  `routes_trip.passenger_fields`. A checked detail is shown AND required at
-  checkout; unchecked ones are hidden entirely.
-
-## [1.1.2] - 2026-07-19
-
-### Fixed
-
-- `Transiting/Manage.tsx`: relaxed the transiting-country select's validation rule from `required|min:1` to `required`. The `min:1` rule was rejecting the field's default value of `0`, making a valid country selection unsubmittable; `required` alone correctly enforces that a country is chosen without misfiring on the `0` sentinel.
-
-Authored by Ferjolt Ozuni. Consolidated from the magus and alvavel whitelabel patch sets into canonical @autobusal source (eliminates per-repo patch-package divergence).