@autobusal/providers 1.30.1 → 1.31.1

package/CHANGELOG.md

@@ -1,5 +1,24 @@
 # Changelog
 
+## 1.31.1
+
+### Fixed
+
+- **A 422 no longer stacks one toast per query.** The search results page
+  asks three endpoints the same question, so a malformed URL rejected three
+  times and showed three identical messages. De-duplicated by the first
+  field error rather than by the message: Laravel's summary appends "(and N
+  more errors)" and each endpoint validates a different rule set, so the
+  three strings differ in that count alone while describing one problem.
+
+## 1.31.0
+
+### Added
+
+- **`PopularRoutesData`** - the city pairs behind the home page's route
+  columns. `from` and `to` arrive localised and `link` is built server-side,
+  so the search URL's date and slug rules live in one place.
+
 ## 1.30.1
 
 ### Fixed

package/Queries/apiClient.ts

@@ -116,9 +116,30 @@ apiClient.interceptors.response.use(response => (
       window.location.href = '/account/documents';
     }
 
-    // if we have a 422 error, we display the message
+    /*
+     * if we have a 422 error, we display the message
+     *
+     * Edited: Ferjolt Ozuni - Date: 2026-08-07
+     *
+     * De-duplicated by the FIRST field error rather than by the message.
+     *
+     * The results page asks three endpoints (dates, departure, alternatives)
+     * the same question, so a malformed URL rejects three times and used to
+     * raise three identical toasts. The obvious key - the message itself -
+     * does not collapse them: Laravel's summary appends "(and N more
+     * errors)", each endpoint validates a different rule set, and so the
+     * three strings differ in that count alone while describing one problem.
+     *
+     * The first entry of `errors` is the same across all three, because it
+     * is the same field the visitor got wrong. That is the cause, and the
+     * cause is what should be shown once.
+     */
     if (error.response.status === 422) {
-      systemError(error.response.data.message);
+      const first = Object.values(
+        (error.response.data.errors ?? {}) as Record<string, string[]>
+      )[0]?.[0];
+
+      systemError(error.response.data.message, first);
     }
 
     // if we have a 500 error, we display a generic error message

package/package.json

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

package/types/locations.ts

@@ -98,4 +98,22 @@ export interface StopData {
   id: number
   name: string
   location: string[]
-}
+}
+/**
+ * A city pair people buy, for the home page's route columns.
+ *
+ * Ferjolt Ozuni - Date: 2026-08-07
+ * `from` and `to` are already localised city names, and `link` is a search
+ * built server-side - the client renders it and never assembles one, so the
+ * date and slug rules live in exactly one place (Traits\Orderable).
+ */
+export interface PopularRouteData {
+  from: string
+  to: string
+  link: string
+}
+
+export interface PopularRoutesData {
+  top: PopularRouteData[]
+  trending: PopularRouteData[]
+}