@rebasepro/types 0.20.0 → 0.20.1-canary.g4d882ca

package/dist/types/admin_block.d.ts

@@ -81,10 +81,15 @@ export declare function nestAdminCollectionKeys(collection: Record<string, unkno
 /**
  * {@link nestAdminKeysOf} for a property, applied to its children too.
  *
- * A map property carries `properties`, an array property carries `of`, and both
- * hold properties with `admin` blocks of their own. A flat `readOnly` left on a
- * child is as dead — and as fatal at the next boot — as one left on the parent,
- * so the walk goes all the way down.
+ * A map property carries `properties`, an array property carries `of`, and an
+ * array of typed blocks carries `oneOf.properties` — a record of properties like
+ * a map's. All of them hold properties with `admin` blocks of their own. A flat
+ * `readOnly` left on a child is as dead — and as fatal at the next boot — as one
+ * left on the parent, so the walk goes all the way down.
+ *
+ * `oneOf` was the container this walk did not know about, and it is the one the
+ * block-based collection templates are built out of: every block inside them
+ * kept its flat `markdown`, and the collection they created would not boot.
  *
  * @group Models
  */

package/dist/types/project_manifest.d.ts

@@ -124,6 +124,30 @@ export interface RebaseStaticAppConfig {
      * static *site* generator emits real files for its routes anyway.
      */
     spa?: boolean;
+    /**
+     * Where this app mounts the Rebase CMS, as a URL path — the address you
+     * would type to reach it, not a path relative to `path`.
+     *
+     * The CMS is an ordinary React component in the developer's own app
+     * (`<RebaseCMS basePath="/admin">`), so its address is a *client-side
+     * route*: nothing on the server, in the bundle, or in the control plane can
+     * observe it. A project whose CMS sits at `/admin` inside a frontend that
+     * also serves a product at `/` is indistinguishable, from the outside, from
+     * one that has no CMS at all — which is exactly how a Rebase Cloud project
+     * came to have no discoverable admin URL anywhere in its console.
+     *
+     * Declaring it is the only way that fact travels. It is carried into the
+     * bundle manifest, recorded on the project's app row at deploy, and is what
+     * lets the console (and `rebase apps list`) offer a link straight to it.
+     *
+     * Must be `path` itself or something beneath it, since the app serving that
+     * URL is the one that has to answer for it. Absent means this app does not
+     * mount the CMS — the common case for a marketing site or a product app.
+     *
+     * @example "/" — the whole app is the CMS, as `rebase init` scaffolds it
+     * @example "/admin" — the CMS is one route of a larger app
+     */
+    cms?: string;
 }
 export type RebaseAppConfig = RebaseBackendAppConfig | RebaseStaticAppConfig;
 /**
@@ -215,7 +239,7 @@ export interface RebaseProjectManifest {
      * Repository-wide opt-out from anonymous CLI usage sharing.
      *
      * **Only `false` does anything.** It suppresses sharing for everyone who
-     * clones this repository, overriding each developer's own opt-in — an
+     * clones this repository, overriding each developer's own answer — an
      * organisation setting policy for work done on its behalf, the same shape
      * as a committed `.npmrc`.
      *
@@ -223,7 +247,7 @@ export interface RebaseProjectManifest {
      * quietly. This file is committed, so a `true` here would be one developer
      * answering a privacy question for every colleague who later clones the
      * repo — consent by proxy, which is the exact thing opt-in exists to
-     * prevent. Individuals opt in with `rebase telemetry enable`.
+     * prevent. Individuals answer at `rebase init`, or with `rebase telemetry enable` / `disable`.
      */
     telemetry?: boolean;
 }
@@ -341,6 +365,27 @@ export interface RebaseBundleStatic {
     dir: string;
     /** Serve `index.html` for unmatched paths under `path`. */
     spa: boolean;
+    /**
+     * The app's name in `rebase.json`.
+     *
+     * `dir` is `static/<name>` and has been since folding was written, so this
+     * is recoverable by string surgery — which is precisely why it is stated
+     * instead. A control plane reconciling app rows against this list has to
+     * match them by name, and a consumer that has to re-derive an identifier
+     * from a path is one refactor away from matching nothing and registering a
+     * duplicate app on every deploy.
+     *
+     * Optional because bundles built before this field exists do not carry it;
+     * a reader that needs a name falls back to the last segment of `dir`.
+     */
+    name?: string;
+    /**
+     * Where this app mounts the Rebase CMS, as a URL path.
+     *
+     * Copied from the app's declaration — see {@link RebaseStaticAppConfig.cms}
+     * for why a client-side route has to be declared to be knowable at all.
+     */
+    cms?: string;
 }
 /**
  * A native module found in the dependency closure.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rebasepro/types",
-  "version": "0.20.0",
+  "version": "0.20.1-canary.g4d882ca",
   "description": "Rebase type definitions — shared interfaces and controller types",
   "keywords": [
     "rebase",