Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: bump @types/aws-lambda #90

Merged
merged 2 commits into from
Jun 20, 2024
Merged

build: bump @types/aws-lambda #90

merged 2 commits into from
Jun 20, 2024

Conversation

onebytegone
Copy link
Contributor

No description provided.

@@ -479,6 +479,10 @@ export default class Request {
const headers = evt.multiValueHeaders || _.mapObject(evt.headers, (v) => { return [ v ]; });

return _.reduce(headers, (memo: StringArrayOfStringsMap, v, k) => {
if (isUndefined(v)) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new types makes many of these props possibly undefined. Thus the addition of these checks.

@coveralls
Copy link

Coverage Status

coverage: 98.669% (-0.7%) from 99.398%
when pulling 64e527b on lambda-types-upgrade
into 42c404d on master.

@onebytegone onebytegone merged commit d47be8a into master Jun 20, 2024
12 of 18 checks passed
@onebytegone onebytegone deleted the lambda-types-upgrade branch June 20, 2024 18:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants