You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/core/event_handler/appsync.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -717,7 +717,7 @@ You can subclass `AppSyncResolverEvent` to bring your own set of methods to hand
717
717
718
718
As you grow the number of related GraphQL operations a given Lambda function should handle, it is natural to split them into separate files to ease maintenance - That's where the `Router` feature is useful.
719
719
720
-
Let's assume you have `app.py` as your Lambda function entrypoint and routes in `users.py`, this is how you'd use the `Router` feature.
720
+
Let's assume you have `app.py` as your Lambda function entrypoint and routes in `location.py`, this is how you'd use the `Router` feature.
721
721
722
722
=== "resolvers/location.py"
723
723
@@ -746,7 +746,7 @@ Let's assume you have `app.py` as your Lambda function entrypoint and routes in
746
746
747
747
=== "app.py"
748
748
749
-
We use `include_router` method and include all location operations registered in the `router` global object.
749
+
We use `include_router` method and include all `location` operations registered in the `router` global object.
0 commit comments