Skip to content

Conversation

@joshuacaron
Copy link
Contributor

Fixes #2795 where res.status gives undescriptive error when the argument is null or undefined. I tested and all other inputs don't seem to have the same issue as null and undefined since they have .toString methods. I added unit tests to verify the new behaviour of res.status.

This is my first pull request on an open source project so if I formatted something wrong or went about submitting this wrong please let me know.

@ebramanti
Copy link

Hope this gets merged, just ran into this issue yesterday!

@dougwilson
Copy link
Contributor

Hi @jadengore , this is a breaking change and is tagged for the 5.x series.

@dougwilson
Copy link
Contributor

Ah, yea, just looked at it and I see now. This is actually the third open PR to add this check. Maybe the other one has the code number check?

@dougwilson
Copy link
Contributor

Sorry, my above comment was made in the wrong PR

@czaarek99
Copy link
Contributor

czaarek99 commented Apr 15, 2018

If we're adding error checking here, is there a reason why we're not just enforcing an integer? If the change is breaking we might as well go all the way?

EDIT: This pull request makes more sense by me.

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

4 participants