@object-ui/i18n 17.5.0 → 17.7.0

package/dist/utils/index.js

@@ -1,4 +1,4 @@
-export { formatDate, formatDateTime, formatRelativeTime, formatCurrency, formatNumber, } from './formatting';
-export { resolvePlural, formatDateSpec, formatNumberSpec, applyLocaleConfig, } from './spec-formatters';
-export { isSpecTranslationData, transformSpecTranslations, } from './spec-translations';
-export { formatDisplayNumber, shouldGroupDisplayNumber, } from './number-display';
+export { formatDate, formatDateTime, formatRelativeTime, formatCurrency, formatNumber, } from './formatting.js';
+export { resolvePlural, formatDateSpec, formatNumberSpec, applyLocaleConfig, } from './spec-formatters.js';
+export { isSpecTranslationData, transformSpecTranslations, } from './spec-translations.js';
+export { formatDisplayNumber, shouldGroupDisplayNumber, } from './number-display.js';

package/dist/utils/spec-formatters.d.ts

@@ -5,29 +5,6 @@
  * This source code is licensed under the MIT license found in the
  * LICENSE file in the root directory of this source tree.
  */
-/**
- * @object-ui/i18n - locale formatting helpers
- *
- * ## Provenance of the four shapes below (objectui#4597)
- *
- * They were authored against `@objectstack/spec/ui`, which exported
- * `PluralRuleSchema`, `DateFormatSchema`, `NumberFormatSchema` and
- * `LocaleConfigSchema` up to and including 17.0.0-rc.5. The pinned
- * 17.0.0-rc.6 removed all four under ADR-0049 enforce-or-remove
- * (objectstack#5055, maintainer ruling 2026-08-06): they carried no key on any
- * authorable shape and nothing ever parsed them, so the vocabulary was retired
- * rather than given a door. The key sets here were faithful to the retired
- * schemas — this is a retirement, not a drift.
- *
- * Nothing in the pinned protocol models locale formatting today, so the
- * interfaces below are declarations this package owns outright, not a view onto
- * a protocol type. The retirement note records that localisation returns as
- * authorable metadata through a new ADR — "the formatter that reads a
- * LocaleConfig first, the vocabulary second" — so re-derive these at that point
- * instead of assuming they still track anything upstream.
- *
- * @module spec-formatters
- */
 /**
  * Plural forms for a single translation key, in CLDR categories.
  *
@@ -83,6 +60,19 @@ export interface SpecDateFormat {
 /**
  * Format a date using a {@link SpecDateFormat} configuration.
  *
+ * A string is read through `toDisplayDate` (`@object-ui/core`), the one parse
+ * step behind the date faces (objectui#10866): a date-only `2026-09-01` names
+ * a calendar day and is rebuilt at local midnight of that day, while a value
+ * with a time part keeps its instant. The engine's own parse read the
+ * date-only form as UTC midnight, so it named August 31st west of UTC, and
+ * for every viewer once `timeZone` was west of UTC.
+ *
+ * `timeZone` therefore applies to an instant only. A date-only value carries
+ * no instant for a zone to place, and the local midnight the shared step
+ * built reads back as its day only in the local zone, so it is formatted
+ * there. A value the shared step refuses, such as a day its month does not
+ * have (objectui#10026), comes back as its string.
+ *
  * @example
  * ```ts
  * formatDateSpec(new Date(), {

package/dist/utils/spec-formatters.js

@@ -5,6 +5,30 @@
  * This source code is licensed under the MIT license found in the
  * LICENSE file in the root directory of this source tree.
  */
+/**
+ * @object-ui/i18n - locale formatting helpers
+ *
+ * ## Provenance of the four shapes below (objectui#4597)
+ *
+ * They were authored against `@objectstack/spec/ui`, which exported
+ * `PluralRuleSchema`, `DateFormatSchema`, `NumberFormatSchema` and
+ * `LocaleConfigSchema` up to and including 17.0.0-rc.5. The pinned
+ * 17.0.0-rc.6 removed all four under ADR-0049 enforce-or-remove
+ * (objectstack#5055, maintainer ruling 2026-08-06): they carried no key on any
+ * authorable shape and nothing ever parsed them, so the vocabulary was retired
+ * rather than given a door. The key sets here were faithful to the retired
+ * schemas — this is a retirement, not a drift.
+ *
+ * Nothing in the pinned protocol models locale formatting today, so the
+ * interfaces below are declarations this package owns outright, not a view onto
+ * a protocol type. The retirement note records that localisation returns as
+ * authorable metadata through a new ADR — "the formatter that reads a
+ * LocaleConfig first, the vocabulary second" — so re-derive these at that point
+ * instead of assuming they still track anything upstream.
+ *
+ * @module spec-formatters
+ */
+import { isRealCalendarDate, toDisplayDate } from '@object-ui/core';
 /**
  * Resolve a plural form based on count, following CLDR plural rules.
  * Uses the Intl.PluralRules API for correct locale-aware pluralization.
@@ -38,6 +62,19 @@ export function resolvePlural(rule, count, locale = 'en') {
 /**
  * Format a date using a {@link SpecDateFormat} configuration.
  *
+ * A string is read through `toDisplayDate` (`@object-ui/core`), the one parse
+ * step behind the date faces (objectui#10866): a date-only `2026-09-01` names
+ * a calendar day and is rebuilt at local midnight of that day, while a value
+ * with a time part keeps its instant. The engine's own parse read the
+ * date-only form as UTC midnight, so it named August 31st west of UTC, and
+ * for every viewer once `timeZone` was west of UTC.
+ *
+ * `timeZone` therefore applies to an instant only. A date-only value carries
+ * no instant for a zone to place, and the local midnight the shared step
+ * built reads back as its day only in the local zone, so it is formatted
+ * there. A value the shared step refuses, such as a day its month does not
+ * have (objectui#10026), comes back as its string.
+ *
  * @example
  * ```ts
  * formatDateSpec(new Date(), {
@@ -48,15 +85,17 @@ export function resolvePlural(rule, count, locale = 'en') {
  * ```
  */
 export function formatDateSpec(date, format, locale = 'en') {
-    const d = date instanceof Date ? date : new Date(date);
+    const d = toDisplayDate(date);
     if (isNaN(d.getTime()))
         return String(date);
+    // The value's shape tells the two apart, the same test the shared step makes.
+    const dateOnly = typeof date === 'string' && isRealCalendarDate(date);
     const options = {};
     if (format.dateStyle)
         options.dateStyle = format.dateStyle;
     if (format.timeStyle)
         options.timeStyle = format.timeStyle;
-    if (format.timeZone)
+    if (format.timeZone && !dateOnly)
         options.timeZone = format.timeZone;
     if (format.hour12 !== undefined)
         options.hour12 = format.hour12;

package/dist/utils/spec-translations.d.ts

@@ -50,9 +50,22 @@ export interface SpecTranslationData {
 /**
  * Detect whether the given record uses the spec `TranslationData` format.
  *
- * Returns `true` when `data.objects` exists and at least one entry has a
- * nested `fields` object (the distinguishing trait vs. an already-flattened
- * namespace tree).
+ * Returns `true` when the payload carries at least one spec translation group
+ * (see {@link SPEC_TRANSLATION_GROUPS}) whose value is an object — every spec
+ * group is a record or an object. A bundle is recognised by ANY group it
+ * carries: one that translates only object labels, apps, pages, dashboards or
+ * flows, with no field label anywhere, is as much a spec payload as one that
+ * translates fields (objectui#10235 — this used to require an
+ * `objects.<n>.fields` entry, and such a bundle was returned untransformed and
+ * read by nothing).
+ *
+ * What stays `false` is the other shape the console's loader accepts: an
+ * i18next resource tree that is already namespaced, as a mock or local-dev
+ * server may return it. Its top-level keys are namespace names — a built-in
+ * pack namespace such as `common`, an app namespace such as `crm`, or `app`,
+ * the one {@link transformSpecTranslations} itself emits — and none of them
+ * is a spec group, so feeding the transform's output back in never wraps it
+ * twice. A group-named key holding a string or an array is not a group either.
  */
 export declare function isSpecTranslationData(data: Record<string, unknown> | null | undefined): data is SpecTranslationData;
 /**

package/dist/utils/spec-translations.js

@@ -23,25 +23,64 @@
  * console transform forgets to copy it, leaving lookups to fall back to the
  * untranslated source label.
  */
+/**
+ * The top-level groups of the translation document the server serves at
+ * `/api/v1/i18n/translations/:locale` — the keys of the `translations` shape
+ * of `@objectstack/spec`'s `GetTranslationsResponseSchema`: every per-app
+ * `TranslationData` group plus the platform-only `settings`, because the
+ * served document is the merge of the app's bundle and the platform's.
+ *
+ * Written out rather than imported: `@object-ui/i18n` deliberately does not
+ * depend on `@objectstack/spec`. The console does, so the pin lives beside
+ * its loader — `apps/console/src/loadLanguage.test.tsx` walks the spec's own
+ * key list and requires a payload carrying any one group, alone, to take the
+ * transform branch. A group the spec adds and this list lacks turns that test
+ * red instead of dropping the group's bundles silently (objectui#10235).
+ */
+const SPEC_TRANSLATION_GROUPS = [
+    'objects',
+    'apps',
+    'messages',
+    'globalActions',
+    'dashboards',
+    'datasets',
+    'pages',
+    'flows',
+    'settings',
+    'metadataForms',
+    'settingsCommon',
+    // `@objectstack/spec` 17.6.0 serves `picklists` (objectstack `addbbf02`, the
+    // `picklist` metadata kind); added at that bump (objectui#11438). The
+    // transform below copies it through onto `app` like any other group.
+    'picklists',
+];
+function isPlainObject(value) {
+    return typeof value === 'object' && value !== null && !Array.isArray(value);
+}
 /**
  * Detect whether the given record uses the spec `TranslationData` format.
  *
- * Returns `true` when `data.objects` exists and at least one entry has a
- * nested `fields` object (the distinguishing trait vs. an already-flattened
- * namespace tree).
+ * Returns `true` when the payload carries at least one spec translation group
+ * (see {@link SPEC_TRANSLATION_GROUPS}) whose value is an object — every spec
+ * group is a record or an object. A bundle is recognised by ANY group it
+ * carries: one that translates only object labels, apps, pages, dashboards or
+ * flows, with no field label anywhere, is as much a spec payload as one that
+ * translates fields (objectui#10235 — this used to require an
+ * `objects.<n>.fields` entry, and such a bundle was returned untransformed and
+ * read by nothing).
+ *
+ * What stays `false` is the other shape the console's loader accepts: an
+ * i18next resource tree that is already namespaced, as a mock or local-dev
+ * server may return it. Its top-level keys are namespace names — a built-in
+ * pack namespace such as `common`, an app namespace such as `crm`, or `app`,
+ * the one {@link transformSpecTranslations} itself emits — and none of them
+ * is a spec group, so feeding the transform's output back in never wraps it
+ * twice. A group-named key holding a string or an array is not a group either.
  */
 export function isSpecTranslationData(data) {
-    if (!data)
+    if (!isPlainObject(data))
         return false;
-    const objects = data.objects;
-    if (!objects || typeof objects !== 'object' || Array.isArray(objects))
-        return false;
-    for (const obj of Object.values(objects)) {
-        if (obj && typeof obj === 'object' && !Array.isArray(obj) && 'fields' in obj) {
-            return true;
-        }
-    }
-    return false;
+    return SPEC_TRANSLATION_GROUPS.some((group) => isPlainObject(data[group]));
 }
 /** Top-level keys that are copied through unchanged onto the `app` namespace. */
 const PASSTHROUGH_TOP_LEVEL_KEYS = [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/i18n",
-  "version": "17.5.0",
+  "version": "17.7.0",
   "type": "module",
   "sideEffects": false,
   "license": "MIT",
@@ -23,6 +23,11 @@
       "import": "./dist/index.js",
       "default": "./dist/index.js"
     },
+    "./locales": {
+      "types": "./dist/locales/index.d.ts",
+      "import": "./dist/locales/index.js",
+      "default": "./dist/locales/index.js"
+    },
     "./locales/*": {
       "types": "./dist/locales/*.d.ts",
       "import": "./dist/locales/*.js",
@@ -30,9 +35,9 @@
     }
   },
   "dependencies": {
-    "i18next": "^26.3.6",
+    "i18next": "^26.4.0",
     "react-i18next": "^17.0.11",
-    "@object-ui/core": "17.5.0"
+    "@object-ui/core": "17.7.0"
   },
   "peerDependencies": {
     "react": "^18.0.0 || ^19.0.0"
@@ -41,7 +46,8 @@
     "@types/react": "19.2.18",
     "react": "19.2.8",
     "typescript": "^6.0.3",
-    "vitest": "^4.1.10"
+    "vitest": "^4.1.10",
+    "@object-ui/test-support": "17.4.0"
   },
   "keywords": [
     "objectui",
@@ -67,8 +73,8 @@
     "LICENSE"
   ],
   "scripts": {
-    "build": "tsc",
-    "test": "vitest run",
+    "build": "tsc && node ../../scripts/check-dist-completeness.mjs",
+    "test": "vitest run --root ../.. packages/i18n/",
     "type-check": "tsc --noEmit && tsc -p tsconfig.test.json",
     "lint": "eslint ."
   }