mirror of
https://github.com/gosticks/DefinitelyTyped.git
synced 2025-10-16 12:05:41 +00:00
8eef7a8374
* [aws-lambda] Keys should be optional inside CloudFrontHeaders According to the AWS documentation, it is optional to specify a `key` for each header value, but the type declaration is currently requiring this to be specified unnecessarily. https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-event-structure.html#lambda-event-structure-response > - `key` (optional) is the case-sensitive name of the header as it appears in an HTTP request; for example, `accept` or `host`. > - If you do not include the header key portion of the key-value pair, Lambda@Edge will automatically insert a header key using the header name that you provide. Regardless of how you've formatted the header name, the header key that is inserted automatically will be formatted with initial capitalization for each part, separated by hyphens (-). > > For example, you can add a header like the following, without a header key: `'content-type': [{ value: 'text/html;charset=UTF-8' }]`. In this example, Lambda@Edge creates the following header key: `Content-Type`. By making this property optional, one is able to write: ```ts import { CloudFrontHeaders } from 'aws-lambda'; const headers: CloudFrontHeaders = { 'content-type': [{ value: 'text/plain '}], }; ``` ... instead of having to repeat the header name like: ```ts import { CloudFrontHeaders } from 'aws-lambda'; const headers: CloudFrontHeaders = { 'content-type': [{ key: 'content-type', value: 'text/plain '}], }; ``` * Update test Setting a header without specifying the key should not raise a TypeScript compiler error. * Revert "Update test" This reverts commit 088653e362e6f0a152f54e9b5694bb778b072354. * Add test for AWSLambda.CloudFrontHeaders with and without explicit keys |
||
|---|---|---|
| .. | ||
| aws-lambda-tests.ts | ||
| index.d.ts | ||
| tsconfig.json | ||
| tslint.json | ||