Override generated query

Which Category is your question related to?

Graphql

Amplify CLI Version

6.0.0

What AWS Services are you utilizing?

Auth, Functions, Graphql, Storage

Provide additional details e.g. code snippets

I have a schema like this:

type Foo @model {
  id: ID!
  .... other attributes
}

I understand that on amplify push, I automatically get the type Query, with getFoo(id: ID). All well.

After a while, I wish to override this query - I want to use the @function directive to call a lambda function for this query only. How do I go about with it? When I tried to define it as:

type Query {
  getFoo(id: ID!): Foo @function(name: "blah")
}

I got the following error on amplify push :

Object type extension 'Query' cannot redeclare field getFoo
An error occurred during the push operation: Object type extension 'Query' cannot redeclare field getFoo

From what I see, I should rename the getFoo query to something else and then attach the function to it. I can no longer use getFoo itself… Is that right or there is a way to override?

[callmekatootie]

@yuth Thank you. Your approach worked. To summarize, in order to override the auto generated query, I had to first remove the existing auto generated one with:

type Foo @model(queries: { get: null, list: "listFoo" }) {
  id: ID!
}

# NOTE: No Query defined further. Just the model type definition above

Then I ran amplify push. After this ran successfully, I then introduced my overridden query:

type Foo @model(queries: { get: null, list: "listFoo" }) {
  id: ID!
}

# NOTE: Below has now been added newly. Above remains untouched
type Query {
   getFoo(id: ID!): Foo @function(name: "blah")
}

and ran amplify push again. This auto generated the listFoo query as well as allowed me to override the getFoo query.

My question has been answered. This issue can now be closed. Thank you for your timely assistance.

[yuth]

@PatrykMilewski you are right. When you override a query, mutation or a subscription, you will have to specify the field names of all the operations that you are not overriding. So in this case the schema will look like if you want the list query to be generated.

type Foo @model(queries: { get: null, list: "listFoo" }) {
  id: ID!
}