@vxil/config 0.12.0 → 0.13.0

package/dist/index.d.ts

@@ -121,6 +121,17 @@ export interface CollectionDef {
      *  `vxil push --allow-destructive`. Any other value fails `vxil plan` /
      *  `vxil push` (it never falls back to 'readwrite'). */
     endUserAccess?: 'readwrite' | 'read' | 'none';
+    /** Role slugs one of which a VERIFIED end user must hold to WRITE this
+     *  collection (create, update, $inc, delete, publish, transaction step,
+     *  filtered delete, batch write, and an end-user delete's cascade into it) —
+     *  otherwise `403 role_required`. Reads are unaffected. Roles are the
+     *  session's verified role claims (its orgs roles — the
+     *  same ones `readRoles` and `caller.roles` in hooks see). Server keys are
+     *  never affected. Absent / `[]` = ungated. Up to 16 slugs
+     *  (`^[a-z0-9][a-z0-9_-]{0,31}$`). Stored on the collection (model data, not
+     *  a config leaf) and carried by BOTH push paths; widening (clearing, or
+     *  adding a role) needs `vxil push --allow-destructive`. */
+    writeRoles?: string[];
     /** Per-record action buttons (guide ch. 4): `[{ key, label, fn }]`, stored on
      *  the collection (model data, not a config leaf). The dashboard renders one
      *  button per action on each record row; `POST /v1/cms/items/:coll/:id/actions/

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vxil/config",
-  "version": "0.12.0",
+  "version": "0.13.0",
   "description": "Typed vxil.config.ts authoring for the vxil backend platform — defineConfig, feature and cms field definitions (published for @vxil/cli).",
   "license": "MIT",
   "homepage": "https://vxil.com",
@@ -23,7 +23,7 @@
     "!src/**/*.test.ts"
   ],
   "dependencies": {
-    "@vxil/feature-configs": "0.10.0"
+    "@vxil/feature-configs": "0.11.0"
   },
   "publishConfig": {
     "access": "public"

package/src/index.ts

@@ -160,6 +160,17 @@ export interface CollectionDef {
    *  `vxil push --allow-destructive`. Any other value fails `vxil plan` /
    *  `vxil push` (it never falls back to 'readwrite'). */
   endUserAccess?: 'readwrite' | 'read' | 'none';
+  /** Role slugs one of which a VERIFIED end user must hold to WRITE this
+   *  collection (create, update, $inc, delete, publish, transaction step,
+   *  filtered delete, batch write, and an end-user delete's cascade into it) —
+   *  otherwise `403 role_required`. Reads are unaffected. Roles are the
+   *  session's verified role claims (its orgs roles — the
+   *  same ones `readRoles` and `caller.roles` in hooks see). Server keys are
+   *  never affected. Absent / `[]` = ungated. Up to 16 slugs
+   *  (`^[a-z0-9][a-z0-9_-]{0,31}$`). Stored on the collection (model data, not
+   *  a config leaf) and carried by BOTH push paths; widening (clearing, or
+   *  adding a role) needs `vxil push --allow-destructive`. */
+  writeRoles?: string[];
   /** Per-record action buttons (guide ch. 4): `[{ key, label, fn }]`, stored on
    *  the collection (model data, not a config leaf). The dashboard renders one
    *  button per action on each record row; `POST /v1/cms/items/:coll/:id/actions/