Skip to content

Commit f7cd398

Browse files
author
Michael Brewer
authored
chore(docs): correct markdown based on markdown lint (#603)
1 parent 173297f commit f7cd398

14 files changed

+1887
-1870
lines changed

Diff for: docs/core/event_handler/api_gateway.md

+465-467
Large diffs are not rendered by default.

Diff for: docs/core/event_handler/appsync.md

+9-6
Original file line numberDiff line numberDiff line change
@@ -170,7 +170,6 @@ This is the sample infrastructure we are using for the initial examples with a A
170170
Value: !GetAtt HelloWorldApi.Arn
171171
```
172172

173-
174173
### Resolver decorator
175174

176175
You can define your functions to match GraphQL types and fields with the `app.resolver()` decorator.
@@ -238,6 +237,7 @@ Here's an example where we have two separate functions to resolve `getTodo` and
238237
```
239238

240239
=== "getTodo_event.json"
240+
241241
```json
242242
{
243243
"arguments": {
@@ -288,6 +288,7 @@ Here's an example where we have two separate functions to resolve `getTodo` and
288288
```
289289

290290
=== "listTodos_event.json"
291+
291292
```json
292293
{
293294
"arguments": {},
@@ -395,6 +396,7 @@ You can nest `app.resolver()` decorator multiple times when resolving fields wit
395396
For Lambda Python3.8+ runtime, this utility supports async functions when you use in conjunction with `asyncio.run`.
396397

397398
=== "async_resolver.py"
399+
398400
```python hl_lines="4 8 10-12 20"
399401
from aws_lambda_powertools import Logger, Tracer
400402

@@ -602,7 +604,6 @@ Use the following code for `merchantInfo` and `searchMerchant` functions respect
602604

603605
You can subclass `AppSyncResolverEvent` to bring your own set of methods to handle incoming events, by using `data_model` param in the `resolve` method.
604606

605-
606607
=== "custom_model.py"
607608

608609
```python hl_lines="11-14 19 26"
@@ -662,8 +663,8 @@ You can subclass `AppSyncResolverEvent` to bring your own set of methods to hand
662663

663664
=== "listLocations_event.json"
664665

665-
```json
666-
{
666+
```json
667+
{
667668
"arguments": {},
668669
"identity": null,
669670
"source": null,
@@ -707,8 +708,8 @@ You can subclass `AppSyncResolverEvent` to bring your own set of methods to hand
707708
"variables": {}
708709
},
709710
"stash": {}
710-
}
711-
```
711+
}
712+
```
712713

713714
## Testing your code
714715

@@ -719,6 +720,7 @@ You can use either `app.resolve(event, context)` or simply `app(event, context)`
719720
Here's an example from our internal functional test.
720721

721722
=== "test_direct_resolver.py"
723+
722724
```python
723725
def test_direct_resolver():
724726
# Check whether we can handle an example appsync direct resolver
@@ -739,6 +741,7 @@ Here's an example from our internal functional test.
739741
```
740742

741743
=== "appSyncDirectResolver.json"
744+
742745
```json
743746
--8<-- "tests/events/appSyncDirectResolver.json"
744747
```

0 commit comments

Comments
 (0)