-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
doc: missing stream.Readable.ReadableState
and stream.Writable.WritableState
#38678
Comments
IIRC, the only way user could access them is |
Related: #445 |
Thanks for reporting. I'll close this: those are not documented because they are private. |
cc @nodejs/streams |
IMO. They are and should remain private (or as private as we can make them). |
Get it. Shall we keep it private, for example, remove this line? node/lib/internal/streams/readable.js Line 39 in 0996eb7
If so I guess it also requires CITGM tests. |
I'm not sure what you'd try to accomplish by removing them. Doing so would require including a deprecation notice and a semver-major cycle. |
None actually, just noticed that they weren't in the documentation but were exposed to the user If this is a costly change, I'm also in favor of keeping it as is. |
Unfortunately it is :(. The general wisdom is to avoid disruption if it could be avoided. |
📗 API Reference Docs Problem
Location
Description
stream.Readable.ReadableState
andstream.Writable.WritableState
are user accessible, but there seems to be no doc of them.submit a pull request.
The text was updated successfully, but these errors were encountered: