@wix/himalaya-cli 0.877.0 → 0.878.0

package/dist/authoring-runtime/node_modules/@wix/himalaya/dist/_types/stdlib/wix-sdk/blog-v3/src/extensions.d.ts

@@ -37,7 +37,18 @@ export interface WixGetPostRequest {
  * filter-by-id — a graceful degrade to the LIST projection (no body) that keeps
  * blog detail + saved screens rendering instead of erroring out. `queryPosts`'s
  * request type has no `fieldsets` field, so that fallback path cannot carry the
- * body. */
+ * body.
+ *
+ * When that fallback ALSO finds nothing (#2658) — a deleted post, or one this
+ * visitor may not see — we reject rather than resolve. `WixGetPostResponse.post`
+ * is non-optional, so returning `{ post: resp.posts?.[0] }` would hand callers an
+ * `undefined` the type promises is present, and the `post.title` access that type
+ * licenses throws a `TypeError` deep inside the caller — the exact hard error
+ * this fallback exists to prevent, and harder to diagnose than a clean rejection.
+ * Every call site rides its own rejection path (cached-post state, draft-only
+ * `catch`, or an `allSettled` filter), so rejecting is what routes them into the
+ * graceful degrade they already implement. The originating failure travels as
+ * `cause`, so the 404-vs-network distinction is not lost. */
 export declare function getPost(postId: string, req?: WixGetPostRequest): Promise<WixGetPostResponse>;
 export interface WixBlogCategory {
     id: string;

package/dist/authoring-runtime/node_modules/@wix/himalaya/dist/wix-blog.mjs

@@ -12,9 +12,13 @@ function getPost(postId, req = {}) {
   return wixCall(
     "GET",
     `/blog/v3/posts/${encodeURIComponent(postId)}` + query
-  ).catch(async () => {
+  ).catch(async (cause) => {
     const resp = await queryPosts({ query: { filter: { id: postId } } });
-    return { post: resp.posts?.[0] };
+    const post = resp.posts?.[0];
+    if (!post) {
+      throw new Error(`Blog post not found: ${postId}`, { cause });
+    }
+    return { post };
   });
 }
 function queryCategories(req = {}) {

package/dist/cli.mjs

@@ -5241,6 +5241,7 @@ function resolveTranslation(value, catalog, sourceCatalog) {
 var BINDING_SIGILS, BINDING_SIGIL_RE, TRANSLATION_PREFIX, TRANSLATION_KEY_RE;
 var init_bindings = __esm({
   "../../core/ts/src/bindings.ts"() {
+    "use strict";
     BINDING_SIGILS = ["service", "flag", "item", "t"];
     BINDING_SIGIL_RE = new RegExp(
       `^\\$(?:${BINDING_SIGILS.filter((s) => s !== "t").join("|")})\\b|^\\$t:`

package/guides/sdk-reference.json

@@ -6590,7 +6590,7 @@
       {
         "name": "getPost",
         "kind": "function",
-        "jsdoc": "/** Fetch a single PUBLISHED post by id — GET /blog/v3/posts/{id}. The list\n * (queryPosts) returns published posts, so the detail reads them here (draft\n * ids are a different space — getDraftPost is for the edit/create flow).\n *\n * Body fieldsets (#826): Blog v3 `GET /posts/{id}` returns 200 but only the\n * LIST projection (title / excerpt / meta) unless the caller asks for the body —\n * the bare GET has NO `richContent` / `contentText`. So we request\n * RICH_CONTENT + CONTENT_TEXT by default and the article body loads on the happy\n * path; callers can override via `req.fieldsets`. (Supersedes the old #507 note:\n * the 502 this GET once returned for anonymous visitors is gone — it 200s now —\n * but a body-less 200 was never the \"body preserved whenever the backend is\n * healthy\" the earlier comment claimed; the body was simply never requested.)\n *\n * On any rejection (network / backend error) we still fall back to a queryPosts\n * filter-by-id — a graceful degrade to the LIST projection (no body) that keeps\n * blog detail + saved screens rendering instead of erroring out. `queryPosts`'s\n * request type has no `fieldsets` field, so that fallback path cannot carry the\n * body. */",
+        "jsdoc": "/** Fetch a single PUBLISHED post by id — GET /blog/v3/posts/{id}. The list\n * (queryPosts) returns published posts, so the detail reads them here (draft\n * ids are a different space — getDraftPost is for the edit/create flow).\n *\n * Body fieldsets (#826): Blog v3 `GET /posts/{id}` returns 200 but only the\n * LIST projection (title / excerpt / meta) unless the caller asks for the body —\n * the bare GET has NO `richContent` / `contentText`. So we request\n * RICH_CONTENT + CONTENT_TEXT by default and the article body loads on the happy\n * path; callers can override via `req.fieldsets`. (Supersedes the old #507 note:\n * the 502 this GET once returned for anonymous visitors is gone — it 200s now —\n * but a body-less 200 was never the \"body preserved whenever the backend is\n * healthy\" the earlier comment claimed; the body was simply never requested.)\n *\n * On any rejection (network / backend error) we still fall back to a queryPosts\n * filter-by-id — a graceful degrade to the LIST projection (no body) that keeps\n * blog detail + saved screens rendering instead of erroring out. `queryPosts`'s\n * request type has no `fieldsets` field, so that fallback path cannot carry the\n * body.\n *\n * When that fallback ALSO finds nothing (#2658) — a deleted post, or one this\n * visitor may not see — we reject rather than resolve. `WixGetPostResponse.post`\n * is non-optional, so returning `{ post: resp.posts?.[0] }` would hand callers an\n * `undefined` the type promises is present, and the `post.title` access that type\n * licenses throws a `TypeError` deep inside the caller — the exact hard error\n * this fallback exists to prevent, and harder to diagnose than a clean rejection.\n * Every call site rides its own rejection path (cached-post state, draft-only\n * `catch`, or an `allSettled` filter), so rejecting is what routes them into the\n * graceful degrade they already implement. The originating failure travels as\n * `cause`, so the 404-vs-network distinction is not lost. */",
         "decl": "export function getPost(\n  postId: string,\n  req: WixGetPostRequest = {},\n): Promise<WixGetPostResponse>;",
         "http": "GET /blog/v3/posts/{…}"
       },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.877.0",
+  "version": "0.878.0",
   "type": "module",
   "description": "himi — the Himalaya authoring CLI. Build a Tier-5 content package on your own machine, push it to the production serve as a draft, preview it on web + Himi Player, and read worker logs back — the remote dev loop. Wraps @himalaya/serve-cli for transport.",
   "keywords": [
@@ -63,5 +63,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "165e76dc8fe6c80270e34398c2070b203234e75c6e6b748b88abb286"
+  "falconPackageHash": "f191342a43dc741dcb30330836f5daafa7f1b917e8a252461dfc1cf2"
 }