You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
strugee opened this issue
Nov 13, 2017
· 3 comments
Labels
docIssues and PRs related to the documentations.eventsIssues and PRs related to the events subsystem / EventEmitter.httpIssues or PRs related to the http subsystem.questionIssues that look for answers.
mscdex
added
events
Issues and PRs related to the events subsystem / EventEmitter.
http
Issues or PRs related to the http subsystem.
question
Issues that look for answers.
labels
Nov 13, 2017
It would make things clearer if we have a better convention on documenting the inheritance/interface implementation, right now it's a bit scattered like:
The request implements the Writable Stream interface. This is an EventEmitter with the following events:
It doesn't seem like there's anything actionable here. If docs need improving perhaps an issue could be opened that mentions what should change so that first time contributors can help out. As is, this hasn't been looked at in 6 months.
docIssues and PRs related to the documentations.eventsIssues and PRs related to the events subsystem / EventEmitter.httpIssues or PRs related to the http subsystem.questionIssues that look for answers.
Maybe I'm just missing something, but AFAIK all instances of
http.ClientRequest
can emiterror
events. However, I can't find any mention of this on https://nodejs.org/api/http.html#http_class_http_clientrequest.The text was updated successfully, but these errors were encountered: