@uniweb/api 1.2.1 → 1.2.2

package/README.md

@@ -360,21 +360,20 @@ keeps it.
 | `min`, `max` on `int`, `decimal` | refuses a value outside them |
 | `format` — `email`, `url` on `string` and `text`; `currency` on `string`; `markdown`, `html` on `text` | checks `email`, `url` and `currency` (an ISO 4217 code); `markdown` and `html` mark what the text is |
 | `localized: true` on text | holds one string for every language, or one per language |
+| `format: year-month` or `format: year` on `date` | holds a month, `2024-05`, or a year, `2024` — ISO 8601's reduced precision, stored as written (a backend from before 2026-10-14 refuses the declaration). With no `format`, a `date` holds a day, `2024-05-14` |
 | `enum: [...]` | keeps the field to those values — in the definition, as its section's `one_of` rule |
 | `type: item_ref`, `options: '@acme/lists/countries'` | keeps the value to an item of that section — an item of another is `409`, `kind: 'rule'` |
 
 A refused value is `kind: 'invalid'`, its `extensions` naming the field (`data.title`,
 `data.label.fr` for one language), the `rule` it broke and the bound
-(`{ rule: 'max_length', max_length: 250 }`). ⚠️ An `enum`'s refusal, `rule: 'one_of'`,
-names its field only in `detail`.
+(`{ rule: 'max_length', max_length: 250 }`, `{ rule: 'format', format: 'year-month' }`). An
+`enum`'s refusal, `rule: 'one_of'`, names its field too — a backend from before 2026-10-14
+names it only in `detail`.
 
 ⛔ **A declaration the backend does not take refuses the whole schema** when it reaches
-the backend, naming the field and the key: a `format` its kind does not have
-(`year-month` on a `date`, `year` on an `int`), a key it does not know (`help`), or one it
-does not check yet (`pattern`, `min_length`).
-
-⚠️ **A `date` is a calendar day**, `YYYY-MM-DD`: `2024-05` is refused. A year alone is an
-`int`, with `min` and `max`.
+the backend, naming the field and the key: a `format` its kind does not have (`month-day`
+on a `date`, `year` on an `int`), a key it does not know (`help`), or one it does not check
+yet (`pattern`, `min_length`).
 
 ### On a section — rules across fields, and across items
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/api",
-  "version": "1.2.1",
+  "version": "1.2.2",
   "description": "The client for a Uniweb site's own backend — session, records, entities — imported by a foundation the way it imports @uniweb/kit.",
   "type": "module",
   "exports": {

package/src/mock/definition.js

@@ -15,11 +15,12 @@
  * | `string` · `text` | `max_length`, `languages`, `format` |
  * | `int` | `min`, `max` |
  * | `decimal` | `precision`, `scale`, `min`, `max` |
+ * | `date` | `format` — `year-month` or `year` |
  * | `item_ref` | `options` (a schema's) → `section_uuid`; `entity_uuid` |
  * | `entity_ref` | `model` (a schema's) → `model_uuid`; `model_uuids`, `contains`, `readable_with` |
  * | `file` | `mime_types`, `max_size` |
  * | `json` | `languages`, `format` |
- * | `bool` · `date` · `datetime` · `secret` | none |
+ * | `bool` · `datetime` · `secret` | none |
  *
  * And what moves: an `enum` becomes its section's `one_of` rule; `multiple: true` is
  * `multi`; a nested section is a section of its own.
@@ -31,6 +32,7 @@ const KIND_KEYS = {
   text: ['max_length', 'languages', 'format'],
   int: ['min', 'max'],
   decimal: ['precision', 'scale', 'min', 'max'],
+  date: ['format'],
   item_ref: ['entity_uuid'],
   entity_ref: ['model_uuids', 'contains', 'readable_with'],
   file: ['mime_types', 'max_size'],

package/src/mock/schema-shape.js

@@ -245,7 +245,18 @@ const TEXT_TYPES = new Set(['string', 'text', 'html', 'markdown', 'email', 'url'
 /** Characters, as the backend counts them — code points, not UTF-16 units. */
 const charCount = (s) => [...s].length
 
-/** `YYYY-MM-DD`, a day the calendar has — the one form a `date` holds (MEASURED 2026-10-14: `2024-5-3` passes, `2024-05` and `2024-02-30` do not). */
+/**
+ * A `date` at the precision its field declares, as the backend checks it (MEASURED 2026-10-14):
+ * `format: year-month` holds `YYYY-MM`, a month `01` to `12`; `format: year` holds `YYYY`; and
+ * with no `format`, a day the calendar has (`2024-5-3` passes, `2024-05` and `2024-02-30` do not).
+ */
+function isDateAt(value, format) {
+  if (format === 'year-month') return /^\d{4}-(0[1-9]|1[0-2])$/.test(value)
+  if (format === 'year') return /^\d{4}$/.test(value)
+  return isDate(value)
+}
+
+/** `YYYY-MM-DD`, a day the calendar has. */
 function isDate(value) {
   const m = /^(\d{4})-(\d{1,2})-(\d{1,2})$/.exec(value)
   if (!m) return false
@@ -406,7 +417,7 @@ export function checkFields(fields, data, path = '') {
 
 /**
  * The bound a value of a field's type breaks, as the backend checks it — `max_length`
- * on text, `min` and `max` on a number, the one form a `date` takes — or null.
+ * on text, `min` and `max` on a number, a `date`'s precision — or null.
  * (MEASURED 2026-10-14, each with the bound beside the rule.)
  */
 function boundOf(field, value, at) {
@@ -419,8 +430,9 @@ function boundOf(field, value, at) {
       return { field: at, rule: 'max', detail: `item.data.${at}=${value} above max=${field.max}`, params: { max: field.max } }
     }
   }
-  if (field.type === 'date' && typeof value === 'string' && !isDate(value)) {
-    return { field: at, rule: 'format', detail: `item.data.${at} is not a valid date (\`${value}\`)`, params: { format: 'date' } }
+  if (field.type === 'date' && typeof value === 'string' && !isDateAt(value, field.format)) {
+    const shape = ['year-month', 'year'].includes(field.format) ? field.format : 'date'
+    return { field: at, rule: 'format', detail: `item.data.${at} is not a valid ${shape} (\`${value}\`)`, params: { format: shape } }
   }
   return null
 }

package/src/mock/store.js

@@ -1149,12 +1149,12 @@ export class MockStore {
     const check = checkItemWrite({ decl: model.decl, section: section.path ?? section.name, data })
     if (check.outcome === OUTCOME.VIOLATES) {
       const first = check.problems[0]
-      // As the backend refuses it (MEASURED 2026-10-14): `reason`, `rule`, the bound beside
-      // it — and the field, except for a `one_of`, which names it only in `detail`.
+      // As the backend refuses it (MEASURED 2026-10-14): `reason`, the field, the `rule` and the
+      // bound beside it — an `enum`'s `one_of` naming its field too, as it has since that day.
       if (first.rule === 'undeclared-section') return refuse(400, 'Validation', first.detail, { field: first.field })
       return refuse(400, 'Validation', first.detail, {
         reason: 'invalid_field',
-        ...(first.rule === 'one_of' ? {} : { field: `data.${first.field}` }),
+        field: `data.${first.field}`,
         rule: first.rule,
         ...(first.params || {}),
       })

package/src/wire.js

@@ -666,7 +666,10 @@ export const READ = {
  *   **`type.data` is the field's whole declaration**: `key`, `kind`, and what the field
  *   declares — `required`, `multi`, `label`, `description`, `localized`, `format`,
  *   `max_length`, `min`, `max` among them. `type` is a wrapper kept from an older
- *   shape: its `id` is always `-1`, and its `name` is the kind.
+ *   shape: its `id` is always `-1`, and its `name` is the kind. ⭐ A `date` field's
+ *   `format` is its precision — `year-month` or `year`, ISO 8601's reduced precision, its
+ *   values `YYYY-MM` or `YYYY` as written — and a `date` with none holds a day (since
+ *   2026-10-14).
  * - **a field of kind `item_ref`** — a choice from a list — carries `section_uuid`, the
  *   section whose items are its choices (a schema's `options:` path becomes it), and
  *   `entity_uuid` when it pins the entry that holds them. Its choices are
@@ -776,9 +779,10 @@ export const SECTION_ITEMS = {
  * | `required` | `field: 'data.title'` |
  * | `max_length` — in characters, per language for a localized value | `field: 'data.title'` (`'data.label.en'`), `max_length` |
  * | `min` · `max` | `field`, and `min` or `max` |
- * | `format` — a `date` that is not `YYYY-MM-DD`, a calendar day; `2024-05` is refused | `field`, `format: 'date'` |
+ * | `format` — a `date` at another precision than its field declares: a day `YYYY-MM-DD`, or with `format: year-month` a month `YYYY-MM`, with `format: year` a year `YYYY` | `field`, `format` — the precision it should be: `'date'`, `'year-month'`, `'year'` |
+ * | `format` — a `string` or `text` that is not its `format`: `email`, `url`, `currency` | `field`, `format` |
  * | `type` | `field` |
- * | `one_of` — a value outside a field's `enum` | ⚠️ **no `field`**: the field is named only in `detail` (`item.level = "x" is not one of the allowed values …`) |
+ * | `one_of` — a value outside a field's `enum` | `field` — since 2026-10-14. ⚠️ A backend from before names the field only in `detail` (`item.level = "x" is not one of the allowed values …`), so read `field` when it is there |
  */
 export const PROBLEM = {
   csrf: 'CSRF Header Required',