@valbuild/shared 0.138.2 → 0.139.0

package/CHANGELOG.md

@@ -1,5 +1,55 @@
 # @valbuild/shared
 
+## 0.139.0
+
+### Minor Changes
+
+- [#776](https://github.com/valbuild/val/pull/776) [`3eb5031`](https://github.com/valbuild/val/commit/3eb503167ae466ee586303c95efcc14665129481) Thanks [@freekh](https://github.com/freekh)! - **Breaking:** `.render({ as: "inline" })` now goes on the list, not on its items.
+
+  You now write `s.array(item).render({ as: "inline" })` and `s.record(item).render({ as: "inline" })`. Each item is then edited in its own row instead of in a preview row you click into. The list decides. The item schema stays reusable, and a page builder made of tagged blocks needs nothing on each block:
+
+  ```ts
+  // before
+  s.array(
+    s.discriminatedUnion(
+      "type",
+      hero.render({ as: "inline" }),
+      text.render({ as: "inline" }),
+    ),
+  );
+
+  // after
+  s.array(s.discriminatedUnion("type", hero, text)).render({ as: "inline" });
+  ```
+
+  What changed:
+
+  - Only `s.array()`, `s.record()` and `s.keyOf()` have `.render(...)` now. On every other schema the method is gone, so the old placement shows up as a type error. Move the render out one level.
+  - The render only affects the list's own items. A list nested inside one of those items keeps its default unless it has its own `.render`.
+  - `s.router()`, `s.imageset()` and `s.fileset()` throw if you give them a render, because pages and media have their own editors.
+  - `s.keyOf(...).render({ as: "inline" })` means the same as before: the selected entry's content is shown below the dropdown.
+
+  **Watch for one case that still compiles:** an array or record that is itself the item of another list. `s.record(s.array(s.string()).render({ as: "inline" }))` used to show the record's arrays inline. Now it shows each array's strings inline. To keep the old layout, write `s.record(s.array(s.string())).render({ as: "inline" })`.
+
+### Patch Changes
+
+- Updated dependencies [[`3eb5031`](https://github.com/valbuild/val/commit/3eb503167ae466ee586303c95efcc14665129481)]:
+  - @valbuild/core@0.139.0
+
+## 0.138.4
+
+### Patch Changes
+
+- [#770](https://github.com/valbuild/val/pull/770) [`0a885b1`](https://github.com/valbuild/val/commit/0a885b1f0304517b167b959958464066194732d0) Thanks [@freekh](https://github.com/freekh)! - Publishing a Git-connected app-mode project now puts your changes on the site in seconds, instead of waiting for CI.
+
+  - The Studio builds the site in the browser, the same way it does for a managed project. Val pushes the commit to your repository as before. When nothing but content has changed since the build the site is serving, the browser's build goes live right away. If a developer has pushed code in between, the site waits for CI's build, so their code is never taken off the site.
+  - If the browser cannot build, the publish still goes through and CI delivers it. This happens when the page is not cross-origin isolated, or when the build keeps failing. Your changes stay visible in the Studio until the site serves a build that has them.
+  - Content that would break a page is caught before anything is pushed to your repository.
+
+- [#771](https://github.com/valbuild/val/pull/771) [`58d13a2`](https://github.com/valbuild/val/commit/58d13a2a534421b341b1bf71d02f0a2290fc0d61) Thanks [@freekh](https://github.com/freekh)! - A project created on val.build with a GitHub repository can publish right away. Before, the first publish was refused with "this deployment was not built from one" until the repository's first CI build had finished.
+
+  While that first build runs, the site is served the template's build. When you publish from it, Val now checks that its content files are exactly the same as the files in your repository. If they are, the publish goes ahead and is pushed to your repository straight away. Your changes stay visible in the Studio until the site serves CI's build of them. If the files differ, the publish is refused, as before.
+
 ## 0.138.2
 
 ### Patch Changes

package/dist/declarations/src/internal/ApiRoutes.d.ts

@@ -1134,6 +1134,7 @@ export declare const Api: {
                     binaryFiles: z.ZodRecord<z.ZodString, z.ZodString>;
                     binaryFilesUnread: z.ZodArray<z.ZodString>;
                     branch: z.ZodNullable<z.ZodString>;
+                    buildable: z.ZodOptional<z.ZodBoolean>;
                 }, z.core.$strip>;
             }, z.core.$strip>]>;
         };

package/dist/declarations/src/internal/publish/contentApi.d.ts

@@ -296,6 +296,20 @@ export type ContentPublishApi = {
                  * branch whose tip is that commit has nothing it has not seen.
                  */
                 gitCommit?: string;
+                /**
+                 * Connected: the tab can build this job (the deployment embeds its
+                 * source). Without it, content goes on to the seal with no build and
+                 * CI builds the push -- which is what a server that predates tab
+                 * builds gets, since it never says so.
+                 */
+                tabBuilds?: true;
+                /**
+                 * Connected, a deployment built from no commit: its Val source files
+                 * (modules and `val.modules.*`), by path from the project root, as git
+                 * blob shas. The content service compares them with the branch when
+                 * there is no commit to compare from.
+                 */
+                deploymentFiles?: Record<string, string>;
             };
             res: {
                 job: PublishTabJob | null;
@@ -310,6 +324,12 @@ export type ContentPublishApi = {
                 ok: boolean;
                 /** A finished build step: the id of the publish (`POST /publish`) it declared. */
                 build?: string;
+                /**
+                 * Connected, at `build`, instead of `build`: this tab cannot build
+                 * (no cross-origin isolation, or a deployment that embeds no source).
+                 * The job goes on without one, and CI builds the push.
+                 */
+                noBuild?: true;
                 /**
                  * A failed step: why, in the tab's words. The step is still retried;
                  * if it fails for good, this is what the editor is told.

package/dist/declarations/src/internal/zod/SerializedSchema.d.ts

@@ -86,9 +86,6 @@ export declare const SerializedSettingsSchema: z.ZodType<SerializedSettingsSchem
  */
 export declare const SerializedValViewSchema: z.ZodObject<{
     type: z.ZodLiteral<"view">;
-    render: z.ZodOptional<z.ZodOptional<z.ZodObject<{
-        as: z.ZodLiteral<"inline">;
-    }, z.core.$strip>>>;
     moduleFilePath: z.ZodType<import("@valbuild/core").ModuleFilePath, unknown, z.core.$ZodTypeInternals<import("@valbuild/core").ModuleFilePath, unknown>>;
     opt: z.ZodLiteral<false>;
     readonly: z.ZodOptional<z.ZodBoolean>;

package/internal/dist/valbuild-shared-internal.cjs.dev.js

@@ -987,7 +987,8 @@ var _excluded = ["directory"];
 
 // A render is static config, so unlike a `preview` it travels WHOLE — this
 // is the field the editor reads the layout from. See `core/src/render.ts`.
-// Every field can carry `{ as: "inline" }`, and that is all a render says.
+// Only array, record and keyOf carry one, and `{ as: "inline" }` is all it
+// says. A stale `render` on any other schema is stripped here, harmlessly.
 // NB: these z.objects STRIP unknown keys, so a render variant that is not
 // declared here is silently dropped in transit — add it here when it is added
 // to `render.ts`.
@@ -1009,7 +1010,6 @@ var FieldRender = InlineRender.optional();
  * - those differ per schema, so there is nothing to share.
  */
 var commonSchemaFields = {
-  render: FieldRender,
   preview: zod.z.literal(true).optional(),
   // Whether the schema declares a `.validate()`. The function cannot serialize,
   // so this flag is what tells the Studio to run the custom validators on the
@@ -1068,6 +1068,7 @@ var SerializedObjectSchema = zod.z.lazy(function () {
 });
 var SerializedArraySchema = zod.z.lazy(function () {
   return zod.z.object(getSitemapTree._objectSpread2(getSitemapTree._objectSpread2({}, commonSchemaFields), {}, {
+    render: FieldRender,
     type: zod.z.literal("array"),
     item: SerializedSchema,
     opt: zod.z["boolean"]()
@@ -1160,6 +1161,7 @@ var SerializedRichTextSchema = zod.z.object(getSitemapTree._objectSpread2(getSit
 }));
 var SerializedRecordSchema = zod.z.lazy(function () {
   return zod.z.preprocess(readLegacyDirectoryAsDir, zod.z.object(getSitemapTree._objectSpread2(getSitemapTree._objectSpread2({}, commonSchemaFields), {}, {
+    render: FieldRender,
     type: zod.z.literal("record"),
     item: SerializedSchema,
     opt: zod.z["boolean"](),
@@ -1176,6 +1178,7 @@ var SerializedRecordSchema = zod.z.lazy(function () {
 });
 var SerializedKeyOfSchema = zod.z.lazy(function () {
   return zod.z.object(getSitemapTree._objectSpread2(getSitemapTree._objectSpread2({}, commonSchemaFields), {}, {
+    render: FieldRender,
     type: zod.z.literal("keyOf"),
     path: SourcePath,
     schema: zod.z.union([zod.z.object({
@@ -1235,7 +1238,6 @@ var SerializedCodeSchema = zod.z.object(getSitemapTree._objectSpread2(getSitemap
 }));
 var SerializedLocaleSchema = zod.z.object({
   type: zod.z.literal("locale"),
-  render: FieldRender,
   preview: zod.z.literal(true).optional(),
   opt: zod.z["boolean"](),
   customValidate: zod.z["boolean"]().optional(),
@@ -1261,7 +1263,7 @@ var SerializedRouteSchema = zod.z.object(getSitemapTree._objectSpread2(getSitema
 
 // A settings module, and each section inside one, serialize as this - the
 // shape is recursive because `items` holds sections which are themselves
-// settings schemas. `s.settings()` never writes render/preview/customValidate
+// settings schemas. `s.settings()` never writes preview/customValidate
 // (see core/src/schema/settings.ts), but they are accepted here because they
 // are part of the declared type.
 var SerializedSettingsSchema = zod.z.lazy(function () {
@@ -1287,7 +1289,6 @@ var SerializedSettingsSchema = zod.z.lazy(function () {
  */
 var SerializedValViewSchema = zod.z.object({
   type: zod.z.literal("view"),
-  render: FieldRender.optional(),
   moduleFilePath: ModuleFilePath$1,
   opt: zod.z.literal(false),
   readonly: zod.z["boolean"]().optional(),
@@ -2657,7 +2658,14 @@ var Api = {
           /** Binary files whose bytes could not be read back. */
           binaryFilesUnread: zod.z.array(zod.z.string()),
           /** The branch the job publishes to. */
-          branch: zod.z.string().nullable()
+          branch: zod.z.string().nullable(),
+          /**
+           * Can the tab build the job from `sourceFiles`? False for a
+           * connected deployment that embeds no source: the tab reports
+           * "no build", and CI builds the push. Absent from older servers,
+           * which only answered buildable jobs.
+           */
+          buildable: zod.z["boolean"]().optional()
         })
       })])
     }

package/internal/dist/valbuild-shared-internal.cjs.prod.js

@@ -987,7 +987,8 @@ var _excluded = ["directory"];
 
 // A render is static config, so unlike a `preview` it travels WHOLE — this
 // is the field the editor reads the layout from. See `core/src/render.ts`.
-// Every field can carry `{ as: "inline" }`, and that is all a render says.
+// Only array, record and keyOf carry one, and `{ as: "inline" }` is all it
+// says. A stale `render` on any other schema is stripped here, harmlessly.
 // NB: these z.objects STRIP unknown keys, so a render variant that is not
 // declared here is silently dropped in transit — add it here when it is added
 // to `render.ts`.
@@ -1009,7 +1010,6 @@ var FieldRender = InlineRender.optional();
  * - those differ per schema, so there is nothing to share.
  */
 var commonSchemaFields = {
-  render: FieldRender,
   preview: zod.z.literal(true).optional(),
   // Whether the schema declares a `.validate()`. The function cannot serialize,
   // so this flag is what tells the Studio to run the custom validators on the
@@ -1068,6 +1068,7 @@ var SerializedObjectSchema = zod.z.lazy(function () {
 });
 var SerializedArraySchema = zod.z.lazy(function () {
   return zod.z.object(getSitemapTree._objectSpread2(getSitemapTree._objectSpread2({}, commonSchemaFields), {}, {
+    render: FieldRender,
     type: zod.z.literal("array"),
     item: SerializedSchema,
     opt: zod.z["boolean"]()
@@ -1160,6 +1161,7 @@ var SerializedRichTextSchema = zod.z.object(getSitemapTree._objectSpread2(getSit
 }));
 var SerializedRecordSchema = zod.z.lazy(function () {
   return zod.z.preprocess(readLegacyDirectoryAsDir, zod.z.object(getSitemapTree._objectSpread2(getSitemapTree._objectSpread2({}, commonSchemaFields), {}, {
+    render: FieldRender,
     type: zod.z.literal("record"),
     item: SerializedSchema,
     opt: zod.z["boolean"](),
@@ -1176,6 +1178,7 @@ var SerializedRecordSchema = zod.z.lazy(function () {
 });
 var SerializedKeyOfSchema = zod.z.lazy(function () {
   return zod.z.object(getSitemapTree._objectSpread2(getSitemapTree._objectSpread2({}, commonSchemaFields), {}, {
+    render: FieldRender,
     type: zod.z.literal("keyOf"),
     path: SourcePath,
     schema: zod.z.union([zod.z.object({
@@ -1235,7 +1238,6 @@ var SerializedCodeSchema = zod.z.object(getSitemapTree._objectSpread2(getSitemap
 }));
 var SerializedLocaleSchema = zod.z.object({
   type: zod.z.literal("locale"),
-  render: FieldRender,
   preview: zod.z.literal(true).optional(),
   opt: zod.z["boolean"](),
   customValidate: zod.z["boolean"]().optional(),
@@ -1261,7 +1263,7 @@ var SerializedRouteSchema = zod.z.object(getSitemapTree._objectSpread2(getSitema
 
 // A settings module, and each section inside one, serialize as this - the
 // shape is recursive because `items` holds sections which are themselves
-// settings schemas. `s.settings()` never writes render/preview/customValidate
+// settings schemas. `s.settings()` never writes preview/customValidate
 // (see core/src/schema/settings.ts), but they are accepted here because they
 // are part of the declared type.
 var SerializedSettingsSchema = zod.z.lazy(function () {
@@ -1287,7 +1289,6 @@ var SerializedSettingsSchema = zod.z.lazy(function () {
  */
 var SerializedValViewSchema = zod.z.object({
   type: zod.z.literal("view"),
-  render: FieldRender.optional(),
   moduleFilePath: ModuleFilePath$1,
   opt: zod.z.literal(false),
   readonly: zod.z["boolean"]().optional(),
@@ -2657,7 +2658,14 @@ var Api = {
           /** Binary files whose bytes could not be read back. */
           binaryFilesUnread: zod.z.array(zod.z.string()),
           /** The branch the job publishes to. */
-          branch: zod.z.string().nullable()
+          branch: zod.z.string().nullable(),
+          /**
+           * Can the tab build the job from `sourceFiles`? False for a
+           * connected deployment that embeds no source: the tab reports
+           * "no build", and CI builds the push. Absent from older servers,
+           * which only answered buildable jobs.
+           */
+          buildable: zod.z["boolean"]().optional()
         })
       })])
     }

package/internal/dist/valbuild-shared-internal.esm.js

@@ -980,7 +980,8 @@ var _excluded = ["directory"];
 
 // A render is static config, so unlike a `preview` it travels WHOLE — this
 // is the field the editor reads the layout from. See `core/src/render.ts`.
-// Every field can carry `{ as: "inline" }`, and that is all a render says.
+// Only array, record and keyOf carry one, and `{ as: "inline" }` is all it
+// says. A stale `render` on any other schema is stripped here, harmlessly.
 // NB: these z.objects STRIP unknown keys, so a render variant that is not
 // declared here is silently dropped in transit — add it here when it is added
 // to `render.ts`.
@@ -1002,7 +1003,6 @@ var FieldRender = InlineRender.optional();
  * - those differ per schema, so there is nothing to share.
  */
 var commonSchemaFields = {
-  render: FieldRender,
   preview: z.literal(true).optional(),
   // Whether the schema declares a `.validate()`. The function cannot serialize,
   // so this flag is what tells the Studio to run the custom validators on the
@@ -1061,6 +1061,7 @@ var SerializedObjectSchema = z.lazy(function () {
 });
 var SerializedArraySchema = z.lazy(function () {
   return z.object(_objectSpread2(_objectSpread2({}, commonSchemaFields), {}, {
+    render: FieldRender,
     type: z.literal("array"),
     item: SerializedSchema,
     opt: z["boolean"]()
@@ -1153,6 +1154,7 @@ var SerializedRichTextSchema = z.object(_objectSpread2(_objectSpread2({}, common
 }));
 var SerializedRecordSchema = z.lazy(function () {
   return z.preprocess(readLegacyDirectoryAsDir, z.object(_objectSpread2(_objectSpread2({}, commonSchemaFields), {}, {
+    render: FieldRender,
     type: z.literal("record"),
     item: SerializedSchema,
     opt: z["boolean"](),
@@ -1169,6 +1171,7 @@ var SerializedRecordSchema = z.lazy(function () {
 });
 var SerializedKeyOfSchema = z.lazy(function () {
   return z.object(_objectSpread2(_objectSpread2({}, commonSchemaFields), {}, {
+    render: FieldRender,
     type: z.literal("keyOf"),
     path: SourcePath,
     schema: z.union([z.object({
@@ -1228,7 +1231,6 @@ var SerializedCodeSchema = z.object(_objectSpread2(_objectSpread2({}, commonSche
 }));
 var SerializedLocaleSchema = z.object({
   type: z.literal("locale"),
-  render: FieldRender,
   preview: z.literal(true).optional(),
   opt: z["boolean"](),
   customValidate: z["boolean"]().optional(),
@@ -1254,7 +1256,7 @@ var SerializedRouteSchema = z.object(_objectSpread2(_objectSpread2({}, commonSch
 
 // A settings module, and each section inside one, serialize as this - the
 // shape is recursive because `items` holds sections which are themselves
-// settings schemas. `s.settings()` never writes render/preview/customValidate
+// settings schemas. `s.settings()` never writes preview/customValidate
 // (see core/src/schema/settings.ts), but they are accepted here because they
 // are part of the declared type.
 var SerializedSettingsSchema = z.lazy(function () {
@@ -1280,7 +1282,6 @@ var SerializedSettingsSchema = z.lazy(function () {
  */
 var SerializedValViewSchema = z.object({
   type: z.literal("view"),
-  render: FieldRender.optional(),
   moduleFilePath: ModuleFilePath$1,
   opt: z.literal(false),
   readonly: z["boolean"]().optional(),
@@ -2650,7 +2651,14 @@ var Api = {
           /** Binary files whose bytes could not be read back. */
           binaryFilesUnread: z.array(z.string()),
           /** The branch the job publishes to. */
-          branch: z.string().nullable()
+          branch: z.string().nullable(),
+          /**
+           * Can the tab build the job from `sourceFiles`? False for a
+           * connected deployment that embeds no source: the tab reports
+           * "no build", and CI builds the push. Absent from older servers,
+           * which only answered buildable jobs.
+           */
+          buildable: z["boolean"]().optional()
         })
       })])
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@valbuild/shared",
-  "version": "0.138.2",
+  "version": "0.139.0",
   "private": false,
   "description": "Val shared types and utilities",
   "repository": {
@@ -37,7 +37,7 @@
     "flexsearch": "^0.8.212",
     "zod": "^4.4.3",
     "zod-validation-error": "^5.0.0",
-    "@valbuild/core": "0.138.2"
+    "@valbuild/core": "0.139.0"
   },
   "files": [
     "CHANGELOG.md",