GeezerVison is showing github.com — docs: fix dead Pants and uvicorn links (#8760) · exg/powertools-lambda-python@35661be
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: docs/core/event_handler/api_gateway.md +1-1Lines changed: 1 addition & 1 deletion - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -1686,7 +1686,7 @@ Each endpoint will be it's own Lambda function that is configured as a [Lambda i |
1686 | 1686 |
|
1687 | 1687 | <!-- markdownlint-disable MD013 --> |
1688 | 1688 | ???+ note |
1689 | | - You can see some of the downsides in this example such as some code reuse. If set up with proper build tooling, the `User` class could be shared across functions. This could be accomplished by packaging shared code as a [Lambda Layer](https://docs.aws.amazon.com/lambda/latest/dg/chapter-layers.html){target="_blank"} or [Pants](https://www.pantsbuild.org/docs/awslambda-python){target="_blank" rel="nofollow"}. |
| 1689 | + You can see some of the downsides in this example such as some code reuse. If set up with proper build tooling, the `User` class could be shared across functions. This could be accomplished by packaging shared code as a [Lambda Layer](https://docs.aws.amazon.com/lambda/latest/dg/chapter-layers.html){target="_blank"} or [Pants](https://www.pantsbuild.org/stable/docs/python/integrations/aws-lambda){target="_blank" rel="nofollow"}. |
1690 | 1690 | <!-- markdownlint-enable MD013 --> |
1691 | 1691 |
|
1692 | 1692 | ## Testing your code |
|
Collapse file
Copy file name to clipboardExpand all lines: docs/includes/_http_resolver_local.md +1-1Lines changed: 1 addition & 1 deletion - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
|
1 | 1 | <!-- markdownlint-disable MD041 MD043 --> |
2 | 2 | #### Http Resolver (ASGI) |
3 | 3 |
|
4 | | -`HttpResolver` is an ASGI-compatible resolver that lets you run your Powertools application with any ASGI server like [uvicorn](https://www.uvicorn.org/){target="_blank"}. It implements the [ASGI specification](https://asgi.readthedocs.io/){target="_blank"}, is lightweight with no external dependencies, and works seamlessly with Lambda or any environment that speaks HTTP. |
| 4 | +`HttpResolver` is an ASGI-compatible resolver that lets you run your Powertools application with any ASGI server like [uvicorn](https://uvicorn.dev/){target="_blank"}. It implements the [ASGI specification](https://asgi.readthedocs.io/){target="_blank"}, is lightweight with no external dependencies, and works seamlessly with Lambda or any environment that speaks HTTP. |
5 | 5 |
|
6 | 6 | If your Lambda is behind [Lambda Web Adapter](https://github.com/awslabs/aws-lambda-web-adapter){target="_blank"} or any other HTTP proxy that speaks the HTTP protocol, it works seamlessly. |
7 | 7 |
|
|