@ampless/backend 0.2.0-alpha.3 → 0.2.0-alpha.5

package/dist/auth/user-admin.d.ts

@@ -1,4 +1,4 @@
-import { AppSyncResolverHandler } from 'aws-lambda';
+import { Handler } from 'aws-lambda';
 
 type AdminRole = 'admin' | 'editor' | 'none';
 interface AdminUserDto {
@@ -6,12 +6,44 @@ interface AdminUserDto {
     email: string;
     role: AdminRole;
 }
-interface ListArgs {
-}
 interface SetArgs {
     userId: string;
     role: string;
 }
-declare const handler: AppSyncResolverHandler<ListArgs | SetArgs, AdminUserDto | AdminUserDto[] | null>;
+/**
+ * Event shape that Amplify Gen 2 actually delivers to a Lambda data
+ * source attached via `a.handler.function()`. The CDK generated
+ * AppSync resource is a PIPELINE resolver whose Lambda-invocation
+ * function uses a VTL request mapping template that emits a flat
+ * payload:
+ *
+ *   {
+ *     "operation": "Invoke",
+ *     "payload": {
+ *       "typeName": "Query",
+ *       "fieldName": "listAdminUsers",
+ *       "arguments": { ... },
+ *       "identity": { ... },
+ *       "source": ..., "request": ..., "prev": ...
+ *     }
+ *   }
+ *
+ * Notably this is NOT the canonical `AppSyncResolverEvent` shape
+ * (which has `event.info.fieldName`). The `aws-lambda` package's
+ * `AppSyncResolverHandler` type is misleading here — typing the
+ * handler with it sends `event.info.fieldName` to `undefined` and
+ * blows up at runtime with
+ * `Cannot read properties of undefined (reading 'fieldName')`.
+ */
+interface UserAdminEvent {
+    typeName: string;
+    fieldName: string;
+    arguments: Partial<SetArgs>;
+    identity?: unknown;
+    source?: unknown;
+    request?: unknown;
+    prev?: unknown;
+}
+declare const handler: Handler<UserAdminEvent, AdminUserDto | AdminUserDto[] | null>;
 
 export { handler };

package/dist/auth/user-admin.js

@@ -76,7 +76,7 @@ async function setAdminUserRole(userPoolId, userId, role) {
 }
 var handler = async (event) => {
   const userPoolId = requireUserPoolId();
-  const field = event.info.fieldName;
+  const field = event.fieldName;
   try {
     if (field === "listAdminUsers") {
       return await listAdminUsers(userPoolId);

package/dist/index.js

@@ -218,7 +218,7 @@ function amplessSchemaModels(a, opts = {}) {
       slug: a.string().required(),
       title: a.string().required(),
       excerpt: a.string(),
-      format: a.enum(["tiptap", "markdown", "html"]),
+      format: a.enum(["tiptap", "markdown", "html", "static"]),
       body: a.json(),
       status: a.enum(["draft", "published"]),
       publishedAt: a.datetime(),
@@ -252,7 +252,7 @@ function amplessSchemaModels(a, opts = {}) {
       pageId: a.id().required(),
       slug: a.string().required(),
       title: a.string().required(),
-      format: a.enum(["tiptap", "markdown", "html"]),
+      format: a.enum(["tiptap", "markdown", "html", "static"]),
       body: a.json(),
       status: a.enum(["draft", "published"]),
       publishedAt: a.datetime()

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ampless/backend",
-  "version": "0.2.0-alpha.3",
+  "version": "0.2.0-alpha.5",
   "description": "Amplify Gen 2 backend factories for ampless: auth, data, storage, event processors, API key renewer",
   "license": "MIT",
   "type": "module",
@@ -56,7 +56,7 @@
     "@aws-sdk/client-sqs": "^3.717.0",
     "@aws-sdk/lib-dynamodb": "^3.717.0",
     "@aws-sdk/util-dynamodb": "^3.717.0",
-    "ampless": "0.2.0-alpha.2"
+    "ampless": "0.2.0-alpha.3"
   },
   "peerDependencies": {
     "@aws-amplify/backend": "^1",