Skip to content

Documentation content issue on 'Extend Amplify-generated resolvers' #5077

@mengyangbai

Description

@mengyangbai

Describe the content issue:
A clear and concise description of what the content issue is. Is there content missing or is there incorrect content?

In the link below:
Upon the next amplify api gql-compile or amplify push the Amplify-generated resolver file will be replaced within the desired slot within the resolver sequence.

amplify/backend/api/<resource_name>
├── build
│   ├── ...
│   ├── resolvers
│   │   ├── ...
│   │   ├── Mutation.createTodo.postAuth.1.req.vtl # Amplify-generated resolvers
│   │   └── ...
|   ...
├── resolvers
│   └── Query.createTodo.postAuth.2.req.vtl # Custom resolver slotted in after postAuth.1 resolver

For example, the a resolver function file named Mutation.createTodo.postAuth.2.req.vtl will be slotted in right after the Mutation.createTodo.postAuth.1.req.vtl resolver. Review the Resolver Mapping Template Programming Guide to learn more about the VTL template.

Error

The error is on code block, we can see that the in the code block, under the resolvers folder is Query.createTodo.postAuth.2.req.vtl while on the paragraph, it is Mutation.createTodo.postAuth.2.req.vtl.

I test with the two name, the Mutation.createTodo.postAuth.2.req.vtl is working while the Query.createTodo.postAuth.2.req.vtl not.

And the Mutation.createTodo.postAuth.2.req.vtl make sense as the name match.

Therefore, could we check and confirm, and update if possible?

URL page where content issue is:
https://docs.amplify.aws/cli/graphql/custom-business-logic/#extend-amplify-generated-resolvers

Metadata

Metadata

Assignees

Labels

amplify/dataIssue related to aws-amplify/amplify-category-apip2incorrect info. ie a bug

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions