@autobusal/providers 1.34.0 → 1.36.0

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 1.36.0
+
+### Added
+
+- **`LabelSettings.locales`** - `{default, available}`, an admin-editable override of `preferences.languages` (which UI locales this label's site responds to, and its default). Null until the new admin-label Locales tab saves one, in which case `preferences.languages` keeps coming from the label's settings.json file exactly as before.
+
+## 1.35.0
+
+### Changed
+
+- **`PageData` (the admin Pages shape) is now locale-object-based, not `_en`/`_sq` columns.** `title`/`content`/`keywords`/`description` are each `LocalizedText` (`Record<string, string>`, one value per locale) - matches obtapi's `pages_content_to_json` migration, which moved `pages` off the two-content-language ceiling onto the same JSON-per-locale shape `faqs` already established. `title_en`/`title_sq`/`content_en`/`content_sq` and friends are gone from the type entirely. New `PageSaveData` covers what the admin save endpoint actually accepts (each field JSON-stringified, not the raw object) - the public page-view response (`@autobusal/page/types.ts`) is unaffected, it was already a single resolved string per field.
+
 ## 1.34.0
 
 ### Added

package/package.json

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

package/types/pages.ts

@@ -1,19 +1,37 @@
+/** One value per locale, e.g. `{ en: "About Us", sq: "Rreth Nesh" }`. */
+export type LocalizedText = Record<string, string>
+
+/**
+ * The ADMIN shape (Pages\AdminController::get()) - title/content/keywords/
+ * description are the raw per-locale objects (Page's own JSON columns,
+ * see the pages_content_to_json migration), unlike the public page-view
+ * response (@autobusal/page/types.ts), which is already resolved to one
+ * locale's plain string.
+ */
 export interface PageData {
   id: number
   name: string
-  name_en?: string
-  name_sq?: string
   internal: string
-  title_en: string
-  title_sq: string
-  content_en: string
-  content_sq: string
+  title: LocalizedText
+  content: LocalizedText
+  keywords: LocalizedText
+  description: LocalizedText
+}
+
+/**
+ * What Pages\AdminController::update() actually accepts - title/content/
+ * keywords/description are each a JSON-STRINGIFIED LocalizedText, not the
+ * raw object PageData carries. Matches the wire shape Content/Ai.tsx
+ * already uses for its own multi-entry field, and avoids the bracket-
+ * notation array fields the BFF proxy can't forward (see the
+ * bff-token-field-collision memory).
+ */
+export interface PageSaveData {
+  name: string
+  internal: string
+  title: string
   content: string
-  keywords_en: string
-  keywords_sq: string
   keywords: string
-  description_en: string
-  description_sq: string
   description: string
 }
 

package/types/settings.ts

@@ -140,6 +140,19 @@ export interface LabelSettings {
   currency: string
   affiliate_max_tickets: number
 
+  /**
+   * Edited: Ferjolt Ozuni - Date: 2026-08-10
+   * Admin-editable override of `preferences.languages` (the label's active
+   * UI locales) - null until an admin saves the Locales tab, in which case
+   * `preferences.languages` keeps coming from the label's settings.json
+   * file, same as before this existed. See Labels\AdminController::
+   * locales() and the add_locales_to_labels_settings migration.
+   */
+  locales?: {
+    default: string
+    available: string[]
+  } | null
+
   legal: {
     kop: string
     njb: string