@palbase/backend 21.0.0 → 21.0.1

package/dist/openapi/index.js

@@ -5990,7 +5990,8 @@ function registerControllerRoute(registry, route) {
     pathParams: route.pathParams,
     returnSchema: route.returnSchema,
     effectiveAuth: route.effectiveAuth,
-    throws: route.throws
+    throws: route.throws,
+    ...route.uploadConfig !== void 0 ? { uploadConfig: route.uploadConfig } : {}
   });
 }
 function registerOperation(registry, op) {
@@ -6038,7 +6039,27 @@ function registerOperation(registry, op) {
     ...security ? { security } : {},
     responses,
     ...refined ? { "x-palbase-refined": true } : {},
-    ...resolvedThrows.length > 0 ? { "x-palbase-errors": errorExtension(resolvedThrows) } : {}
+    ...resolvedThrows.length > 0 ? { "x-palbase-errors": errorExtension(resolvedThrows) } : {},
+    // WHAT MAKES AN UPLOAD ROUTE AN UPLOAD ROUTE, to every generator.
+    //
+    // An `@Upload` route's bytes never pass through the backend: the client
+    // PUTs them straight at a signed URL the authorize pre-flight mints, and
+    // the decorated method is the completion handler. Nothing about that is
+    // visible in the request body — the pre-flight body is ordinary JSON — so a
+    // document without this extension describes an upload route as a plain
+    // POST, and every client generated from it has NO WAY TO SEND A FILE.
+    //
+    // Measured 2026-08-24 against centauri: the Swift generator reads
+    // `x-palbase-upload` (palbase-swiftgen Parse.swift) and, finding none,
+    // emitted `PBEndpoint` instead of `PBUploadEndpoint` — `uploadImage` lost
+    // its `file:` parameter and the app stopped compiling. Photo upload and
+    // identity verification, both gone, from an absent extension.
+    ...op.uploadConfig !== void 0 ? {
+      "x-palbase-upload": {
+        bucket: op.uploadConfig.bucket,
+        pathTemplate: op.uploadConfig.pathTemplate
+      }
+    } : {}
   });
 }
 function resolveThrows(throws) {