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.

Sign up for GitHub

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

Jump to bottom

Eventually support IncomingMessage/OutgoingMessage #15

Open
dougwilson opened this issue Dec 12, 2014 · 1 comment
Open

Eventually support IncomingMessage/OutgoingMessage #15

dougwilson opened this issue Dec 12, 2014 · 1 comment
Assignees
@dougwilson
Labels
ideas

Comments

@dougwilson
Copy link
Contributor

Right now the signature is fresh(reqHeaders, resHeaders), which is of course nice for being agnostic, but slightly lame. I don't think we should remove this "agnostic-ness" per-se, but it would be nice to pass in IncomigMessage and OutgoingMessage objects so this lib can just handle weirdness like expressjs/express#2468
@dougwilson dougwilson self-assigned this Dec 12, 2014
@dougwilson
Copy link
Contributor Author

We can also move the statusCode and method checking or whatever in here as well if this happens, similar to type-is does with hasBody to make it easier to conform to HTTP specs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dougwilson dougwilson

Labels
ideas
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dougwilson