Move awslambda HttpResponseStream/streamifyResponse to the aws-sdk or its own package?

Open
#74 4 comments 13 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, node.js, typescript
Domain
cloud

Research direction

The issue names streamifyResponse, HttpResponseStream, HttpResponseStream.from, the AWS Lambda runtime, and the lambda-stream wrapper, but no repository files or tests. Start by comparing the existing runtime interfaces with lambda-stream and determine whether extracting them into the aws-sdk or a separate package is intended; done would require a decided package location and full interface compatibility.

Written by the indexing model from the issue text.

Description

The fact that streamifyResponse and HttpResponseStream are only available embedded in the runtime makes it difficult to write simple, coherent unit tests for streaming lambda handlers. There's been at least one good attempt to create a wrapper to support easy testing, but it's not completely interface compatible (lacking, for example, the HttpResponseStream.from(underlyingStream, prelude) method) and it seems wasteful to rewrite/repackage code that's already written just to unbundle it from the rest of the NodeJS runtime.

Dominant language
TypeScript
Stars
224
Forks
60
Avg merge
26m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/aws-lambda-nodejs-runtime-interface-client

All issues in aws/aws-lambda-nodejs-runtime-interface-client

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.