Mutation arguments does not accept customType

[OperationalFallacy]

Environment information

latest packages

Description

In gen1 I could do this

input UserInput {
  securityId: ID!
  docId: someEnum
}

type Mutation {
  requestOperation(input: UserInput!): Document // input is a custom type and output is a model

Gen2 shows an error if I use custom type in the arguments

requestOperation a
.mutation()
.arguments({
  input: a.ref("UserInput")
})

It was convenient since front-end would get strongly typed, separate interfaces for the input

[ykethan]

Hey,👋 thanks for raising this! I'm going to transfer this over to our API repository for better assistance 🙂

[chrisbonifacio]

Hi @OperationalFallacy this is currently expected behavior. Using a.ref does not dereference model fields when passed to custom query/mutation arguments.you have to explicitly list the fields. Same with referencing an enum, online inline enums are supported.

I will mark this as a feature request for the team to consider.

[kfinley-rbi]

Hi @chrisbonifacio,

I think we might have raised a duplicate here:
#435

What would be the work around if we nested arrays what we want to pass to an AppSync resolver or lambda?

Item: a.customType({
  modifiers: a.string().array(),
}),

updateItems: a
  .mutation()
  .arguments({
    items: a.ref('Item').array(),
  })

We could flatten it, but then we would need to track the relations relationships manually.

updateItems: a
.mutation()
.arguments({
  items: a.string().array(),
  modifiers: a.string().array(),
})

All suggestions would be helpful. Thank you!