axs add resolver

axs add resolver is schema-aware: it reads your AppSync schema, offers the type/field targets, and scaffolds a VTL or JS UNIT resolver wired to a data source. Interactive when the field is omitted. See GraphQL API.

On a feature-layout graphql project (conventions.resolverLocation: "colocated"), pass --feature <feature> so the artifacts land in lambdas/features/<feature>/resolvers/; the CLI prompts for it when omitted on a TTY and fails fast without it non-interactively. On a module-layout project (resolverLocation: "central") artifacts go to assets/resolvers/ and --feature is rejected. See Layout: Module vs Feature.

axs add resolver Query.listItems --type js --data-source ItemsTable

The full option surface is generated from the CLI itself:

Usage: axs add resolver [field]

Add a vtl or js AppSync resolver (schema-aware; interactive when omitted)

Arguments:
  field

Options:
  --type <type>                 Resolver type: vtl | js
  --api <constructId>           Target API when the project has more than one
  --data-source <name>          Data source name
  --feature <feature>           Owning feature for colocated resolver trees (graphql feature layout)
  --no-test                     Reserved no-op (resolvers emit no colocated test in 3J7)
  --local                       Local mode — skips auth check