-
Notifications
You must be signed in to change notification settings - Fork 30k
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
[WIP] doc: better stream docs #19143
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -28,10 +28,13 @@ objects will rarely (if ever) have need to use the `stream` module directly. | |
|
||
## Organization of this Document | ||
|
||
This document is divided into two primary sections with a third section for | ||
This document is divided into four primary sections with a fifth section for | ||
additional notes. The first section explains the elements of the stream API that | ||
are required to *use* streams within an application. The second section explains | ||
the elements of the API that are required to *implement* new types of streams. | ||
The third section is geared towards explanations and *code examples*. The fourth | ||
section showcases important *npm modules* that make working with streams | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not sure we really want to implement a section like that to be honest. In the past, we've avoided the appearance of promoting certain modules over their competitors. We'd want to be very careful about that. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sounds good! I can get rid of the specific section and maybe instead have examples that use those modules? |
||
easier. | ||
|
||
## Types of Streams | ||
|
||
|
@@ -2202,6 +2205,10 @@ stream that simply passes the input bytes across to the output. Its purpose is | |
primarily for examples and testing, but there are some use cases where | ||
`stream.PassThrough` is useful as a building block for novel sorts of streams. | ||
|
||
## Explanations and Code Examples | ||
|
||
## Important NPM Modules | ||
|
||
## Additional Notes | ||
|
||
<!--type=misc--> | ||
|
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.
Nit: "geared towards explanations" is less informative than this should be IMO. Maybe this?
Or perhaps even better, this?
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.
Sounds good! Will update