@autobusal/common 1.33.9 → 1.33.10

package/Autocomplete/Autocomplete.tsx

@@ -4,6 +4,7 @@ import { UseFormRegister, UseFormSetValue } from 'react-hook-form';
 import { useOutside } from '@autobusal/hooks';
 import { Validate } from '@autobusal/utilities';
 import Suggestions from './Suggestions';
+import { fold } from './fold';
 import { Container } from './styles';
 import { AutocompleteData } from './types';
 
@@ -49,9 +50,11 @@ const Autocomplete = ({ name, label, defaultValue, data, validation, t, refs, on
     // eslint-disable-next-line react-hooks/exhaustive-deps
   }, [ data ]);
 
-  const options = data.filter(item => {
-    return item.name.toLowerCase().indexOf(q.toLowerCase()) > -1;
-  });
+  const needle = fold(q);
+
+  const options = data.filter(item => (
+    [ item.name, ...(item.search ?? []) ].some(candidate => fold(candidate).includes(needle))
+  ));
 
   const onChange = (event: ChangeEvent<HTMLInputElement>): void => {
     setQ(event.target.value);

package/Autocomplete/fold.ts

@@ -0,0 +1,27 @@
+/**
+ * Case- and accent-insensitive form of a string, for matching only.
+ *
+ * Claude - Date: 2026-08-21
+ *
+ * The search box compared raw lowercased strings, which quietly failed on
+ * this platform's most common names: in Albanian the cities are Korcë,
+ * Vlorë, Shkodër and Kukës, so typing "korce", "vlore", "shkoder" or
+ * "kukes" - which is how anybody without an Albanian keyboard layout types
+ * them, and how the ENGLISH spellings are written - matched nothing at all.
+ *
+ * The mobile app has always done this (src/lib/cities.ts); the web never
+ * got the same treatment.
+ *
+ * NFD splits an accented character into its base letter plus a combining
+ * mark, and the range below is the Unicode combining-diacritics block, so
+ * "ë" becomes "e" and "ç" becomes "c" without a per-language table. It is
+ * deliberately not a full transliteration: Cyrillic and Greek are left
+ * alone, because those are the scripts people type those names IN, and
+ * `search` carries the Latin spellings alongside them anyway.
+ */
+export const fold = (value: string): string => (
+  value
+    .toLowerCase()
+    .normalize('NFD')
+    .replace(/[\u0300-\u036f]/g, '')
+);

package/Autocomplete/types.ts

@@ -1,4 +1,20 @@
 export interface AutocompleteData {
+  /** What the option shows - already in the visitor's language */
   name: string
+
   value: string
-}
+
+  /**
+   * Extra spellings this option should MATCH on but never display.
+   *
+   * Claude - Date: 2026-08-21
+   *
+   * Matching has to be language-blind even though display is not. A Greek
+   * typing "Θεσσαλονίκη", a Serb typing "Solun" and an Englishman typing
+   * "Thessaloniki" all mean the same city, and none of them should have to
+   * be browsing in the right language to find it. FlixBus behaves the same
+   * way - their autocomplete returns one city id for all three queries and
+   * only the LABEL changes with the interface language.
+   */
+  search?: string[]
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@autobusal/common",
-  "version": "1.33.9",
+  "version": "1.33.10",
   "author": "Ferjolt Ozuni",
   "type": "module",
   "main": "index.ts"