Add TypeScript generic support for Request and Response types #292
+176
−22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds comprehensive TypeScript generic support to lambda-api's
Request
andResponse
types, enabling developers to create strongly-typed APIs with better compile-time safety.Key Changes
Generic Type Definitions
Usage Example
Benefits
Backwards Compatibility
All existing lambda-api code continues to work without changes. The generic types have sensible defaults:
Request
defaults toRequest<{[key: string]: string | undefined}, {[key: string]: string | undefined}, any>
Response
defaults toResponse<any>
Developers can gradually adopt the new generic types at their own pace.
Testing
Fixes #244.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.