@ampless/backend 0.2.0-alpha.12 → 0.2.0-alpha.14

package/dist/functions/mcp-handler.js

@@ -627,17 +627,26 @@ async function validateBearer(plaintext) {
   );
   const row = res.Item;
   if (!row?.value) return null;
-  let meta;
-  try {
-    meta = JSON.parse(row.value);
-  } catch {
-    console.error("[mcp-handler] could not parse token row", { hash });
+  const meta = decodeTokenMeta(row.value);
+  if (!meta) {
+    console.error("[mcp-handler] could not decode token row", { hash, valueType: typeof row.value });
     return null;
   }
   if (meta.revokedAt) return null;
   if (meta.expiresAt && new Date(meta.expiresAt).getTime() <= Date.now()) return null;
   return meta;
 }
+function decodeTokenMeta(value) {
+  if (typeof value === "object") return value;
+  if (typeof value === "string") {
+    try {
+      return JSON.parse(value);
+    } catch {
+      return null;
+    }
+  }
+  return null;
+}
 var cachedCtx = null;
 function makeContext(meta) {
   if (cachedCtx && cachedCtx.defaultSiteId === (meta.scope.siteId ?? "default")) {

package/dist/index.d.ts

@@ -217,6 +217,14 @@ interface AmplessSchemaAuthorizationOpts {
  * `amplify/data/resource.ts`. When no Lambda function refs are
  * supplied the function returns `[]`, so the schema stays unaffected.
  *
+ * Return type is `any[]` (matching the rest of this module's
+ * intentional looseness around `@aws-amplify/data-schema`'s heavily
+ * generic builder types) so callers don't have to wrestle the
+ * generic `SchemaAuthorization<…>` parameters that change between
+ * minor versions. `amplify/data/resource.ts` strict-type-checks fine
+ * downstream because the schema itself still resolves through
+ * `ClientSchema<typeof schema>` correctly.
+ *
  * Usage:
  *
  *     const schema = a.schema({
@@ -226,7 +234,7 @@ interface AmplessSchemaAuthorizationOpts {
  *       mcpHandlerFunction: mcpHandler,
  *     }))
  */
-declare function amplessSchemaAuthorization(allow: any, opts?: AmplessSchemaAuthorizationOpts): unknown[];
+declare function amplessSchemaAuthorization(allow: any, opts?: AmplessSchemaAuthorizationOpts): any[];
 /**
  * Standard authorization modes for ampless. `userPool` is the default
  * (admin/editor access); the API key serves the public read endpoints

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ampless/backend",
-  "version": "0.2.0-alpha.12",
+  "version": "0.2.0-alpha.14",
   "description": "Amplify Gen 2 backend factories for ampless: auth, data, storage, event processors, API key renewer",
   "license": "MIT",
   "type": "module",