@localess/schema 4.0.2-dev.20260929183905 → 4.0.2-dev.20260930092045

package/README.md

@@ -131,13 +131,13 @@ export type ContentData = InferContentData<typeof config>;
 export type PageContent = InferContent<typeof Page, typeof config>;
 ```
 
-`PageContent` now has `title: string`, `buttons: ButtonContent[]`, and `type: 'primary' | 'secondary'` on each button — the enum narrowed to a literal union, resolved through the nesting. Change `minLength` in the schema and nothing breaks; rename a field and every call site fails to compile.
+`PageContent` now has `title?: string`, `buttons?: ButtonContent[]`, and `type: 'primary' | 'secondary'` on each button — the enum narrowed to a literal union, resolved through the nesting. Change `minLength` in the schema and nothing breaks; rename a field and every call site fails to compile.
 
 Use it with the client:
 
 ```ts
 const content = await client.getContentBySlug<PageContent>('home', { locale: 'en' });
-content.data.buttons[0].type; // 'primary' | 'secondary'
+content.data.buttons?.[0].type; // 'primary' | 'secondary' | undefined
 ```
 
 `InferEnum<typeof ButtonType>` gives you the value union on its own.

package/SKILL.md

@@ -82,7 +82,7 @@ Everything below is `export type` — importable with `import type { ... } from
 | Inference (from `infer.ts`) | `InferContentData`, `InferContent`, `InferEnum` |
 | Validation (from `validate.ts`) | `ValidationIssue` (`{ severity: 'error' \| 'warning'; code; path; message }`), `ValidationResult` (`{ ok; issues }`) |
 | Wire model (re-exported from `@localess/model`) | `SchemaType`, `SchemaFieldKind`, `AssetFileType`, `SchemaEnumValue`, `SchemaFieldBase`, `SchemaField`, the 18 per-kind interfaces (`SchemaFieldText`, `SchemaFieldTextarea`, `SchemaFieldRichText`, `SchemaFieldMarkdown`, `SchemaFieldNumber`, `SchemaFieldColor`, `SchemaFieldDate`, `SchemaFieldDateTime`, `SchemaFieldBoolean`, `SchemaFieldOption`, `SchemaFieldOptions`, `SchemaFieldLink`, `SchemaFieldReference`, `SchemaFieldReferences`, `SchemaFieldAsset`, `SchemaFieldAssets`, `SchemaFieldSchema`, `SchemaFieldSchemas`), `SchemaComponentExport`, `SchemaEnumExport`, `SchemaExport` |
-| Content values (re-exported from `@localess/model`) | `ContentAsset`, `ContentLink`, `ContentReference`, `ContentRichText` |
+| Content values (re-exported from `@localess/model`) | `ContentAsset`, `ContentLink`, `ContentReference`, `ContentRichText` — plus every other `@localess/model` type (`Content`, `Locale`, `Space`, `Translations`, …), since `src/index.ts` ends with `export * from '@localess/model'` |
 
 ## `defineField`
 
@@ -178,7 +178,7 @@ schema in the config is checked, not just the first. Rules and their `code`:
 | `field/schema-ref-is-enum` | ...and that schema must be `ROOT` or `NODE`, not `ENUM`. |
 
 `validate` does not check for stray properties from the wrong field kind —
-use `defineField` for that (below). Duplicate field names and duplicate
+use `defineField` for that (above). Duplicate field names and duplicate
 schema ids are not validation issues either: `defineSchema`/`defineConfig`
 throw on them as programming errors.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@localess/schema",
-  "version": "4.0.2-dev.20260929183905",
+  "version": "4.0.2-dev.20260930092045",
   "description": "Programmatic schema definitions for Localess with TypeScript content type inference.",
   "keywords": [
     "localess",
@@ -43,7 +43,7 @@
   },
   "license": "MIT",
   "dependencies": {
-    "@localess/model": "4.0.2-dev.20260929183905"
+    "@localess/model": "4.0.2-dev.20260930092045"
   },
   "devDependencies": {
     "@types/node": "^24",