-
-
Notifications
You must be signed in to change notification settings - Fork 49
use writableEnd instead finished #54
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.
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
Conversation
Phillip9587
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer to use msg.writableEnded without a helper function as we plan to only support Node.js 18+ in v3.
|
@UlisesGascon @Phillip9587 I’d prefer to make this change for version 2, and it can be backported to v3. |
|
@bjohansebas Can you rebase the PR and remove the |
|
done, i’ve already done the rebase |
ctcpip
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.
Co-authored-by: Chris de Almeida <[email protected]>
Co-authored-by: Chris de Almeida <[email protected]>
…deprecated finished Ref: jshttp#54
It is recommended to use that property over finished
https://nodejs.org/api/http.html#responsefinished
https://nodejs.org/api/deprecations.html#DEP0136
https://nodejs.org/api/http.html#requestwritableended