Throw TypeError if argument passed to res.status is null or undefined

[Shastel]

It's fix for #2795

[dougwilson]

Hi @Shastel , thanks for the pull request! I see in the issue you linked, it was said that #2797 is made to fix that issue. Is this pull request a duplicate of #2797 ? If not, in what ways does it differ?

[Shastel]

Hi @dougwilson, It's not a duplicate, but generally it's almost same as #2797 . But that pr has not any progress almost year

[dougwilson]

Hi @Shastel, that PR is just pending merge into 5.x. Unless there is something you feel is wrong with it, we have full intention on merging that into 5.x. I do appreciate you making the pull request, but I don't want to disregard that user's PR and instead use this one unless there is something different about this one.

[dougwilson]

To summarize, I can use this one over the other, but I wasn't aware of anything wrong with the other. If it's not a duplicate and there is something different, please explain the differences so we can understand which one to accept. Otherwise, we'll default to the one that came first is all I'm saying.

[Shastel]

My pr hasn't unnecessary else statement.
And also we also should ask @joshuacaron about any progress

[dougwilson]

And also we also should ask @joshuacaron about any progress

Progress of what?

[Shastel]

@dougwilson sorry, i have misunderstanding with flow.
So if from yours point of view difference between pr's is not critical we should close my pr.

[dougwilson]

I can use this one over the other, but I wasn't aware of anything wrong with the other. If it's not a duplicate and there is something different, please explain the differences so we can understand which one to accept. Otherwise, we'll default to the one that came first is all I'm saying.