Merge branch 'develop' into develop

Author: leandrodamascena

CHANGELOG.md

@@ -4,12 +4,21 @@
 <a name="unreleased"></a>
 # Unreleased
 
+## Bug Fixes
+
+* **docs:** correct build optimization script and docs ([#7367](https://github.com/aws-powertools/powertools-lambda-python/issues/7367))
+
 ## Code Refactoring
 
 * **parser:** Improve AppSync models with examples and descriptions ([#7330](https://github.com/aws-powertools/powertools-lambda-python/issues/7330))
 
+## Documentation
+
+* **event_handler:** add info section about types ([#7368](https://github.com/aws-powertools/powertools-lambda-python/issues/7368))
+
 ## Features
 
+* **event_handler:** enhance OpenAPI response with headers, links, examples and encoding ([#7312](https://github.com/aws-powertools/powertools-lambda-python/issues/7312))
 * **parser:** add field metadata and examples for CloudWatch models ([#7343](https://github.com/aws-powertools/powertools-lambda-python/issues/7343))
 
 ## Maintenance

docs/build_recipes/performance-optimization.md

@@ -7,6 +7,8 @@ description: Optimize Lambda functions for better performance and reduced costs
 
 Optimize your Lambda functions for better performance, reduced cold start times, and lower costs. These techniques help minimize package size, improve startup speed, and reduce memory usage.
 
+Always validate your function's behavior after applying optimizations to ensure an optimization hasn't introduced any issues with your packages. For example, removal of directories that appear to be unnecessary, such as `docs`, can break some libraries.
+
 ## Reduce cold start times
 
 1. **Minimize package size** by excluding unnecessary files

docs/core/event_handler/api_gateway.md

@@ -1493,6 +1493,9 @@ Each endpoint will be it's own Lambda function that is configured as a [Lambda i
 
 You can test your routes by passing a proxy event request with required params.
 
+???+ info
+    Fields such as headers and query strings are always delivered as strings when events reach Lambda. When testing your Lambda function with local events, we recommend using the sample events available in our [repository](https://github.com/aws-powertools/powertools-lambda-python/tree/develop/tests/events).
+
 === "API Gateway REST API"
 
     === "assert_rest_api_resolver_response.py"
@@ -1556,14 +1559,3 @@ You can test your routes by passing a proxy event request with required params.
 Chalice is a full featured microframework that manages application and infrastructure. This utility, however, is largely focused on routing to reduce boilerplate and expects you to setup and manage infrastructure with your framework of choice.
 
 That said, [Chalice has native integration with Lambda Powertools](https://aws.github.io/chalice/topics/middleware.html){target="_blank" rel="nofollow"} if you're looking for a more opinionated and web framework feature set.
-
-**What happened to `ApiGatewayResolver`?**
-
-It's been superseded by more explicit resolvers like `APIGatewayRestResolver`, `APIGatewayHttpResolver`, and `ALBResolver`.
-
-`ApiGatewayResolver` handled multiple types of event resolvers for convenience via `proxy_type` param. However,
-it made it impossible for static checkers like Mypy and IDEs IntelliSense to know what properties a `current_event` would have due to late bound resolution.
-
-This provided a suboptimal experience for customers not being able to find all properties available besides common ones between API Gateway REST, HTTP, and ALB - while manually annotating `app.current_event` would work it is not the experience we want to provide to customers.
-
-`ApiGatewayResolver` will be deprecated in v2 and have appropriate warnings as soon as we have a v2 draft.

examples/build_recipes/build_optimization/optimize-advanced.sh

@@ -15,7 +15,6 @@ find build/ -name "*.so.*" -exec strip --strip-debug {} \; 2>/dev/null || true
 rm -rf build/*/site-packages/*/tests/
 rm -rf build/*/site-packages/*/test/
 rm -rf build/*/site-packages/*/.git/
-rm -rf build/*/site-packages/*/docs/
 rm -rf build/*/site-packages/*/examples/
 rm -rf build/*/site-packages/*/*.md
 rm -rf build/*/site-packages/*/*.rst

examples/build_recipes/build_optimization/optimize-package.sh

@@ -7,8 +7,7 @@ find build/ -name "*.dist-info" -type d -exec rm -rf {} +
 find build/ -name "tests" -type d -exec rm -rf {} +
 find build/ -name "test_*" -delete
 
-# Remove documentation and examples
-find build/ -name "docs" -type d -exec rm -rf {} +
+# Remove examples
 find build/ -name "examples" -type d -exec rm -rf {} +
 
 echo "✅ Package optimized"