Throws error if undefined status code is sent #2082
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mcollina
reviewed
Feb 5, 2020
mcollina
requested changes
Feb 6, 2020
|
ci is failing on Node 6. |
Eomm
added
v2.x
Eomm
reviewed
Feb 7, 2020
leorossi
force-pushed
the
bugfix/truncated-response-on-undefined-statuscode
branch
from
87704d4
to
8386175
Compare
Eomm
approved these changes
Feb 13, 2020
This was referenced Apr 12, 2020
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When setting an
undedinedstatus code in reply, it will throw a new custom error message.Fixes #2078
Checklist
npm run testandnpm run benchmark