Skip to content
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

Should Socket.readable/writeable be documented? #22037

Closed
ronkorving opened this issue Jul 31, 2018 · 1 comment
Closed

Should Socket.readable/writeable be documented? #22037

ronkorving opened this issue Jul 31, 2018 · 1 comment
Labels
doc Issues and PRs related to the documentations. net Issues and PRs related to the net subsystem.

Comments

@ronkorving
Copy link
Contributor

  • Version: 10.7.0
  • Platform: all
  • Subsystem: docs

net.Socket has 2 very useful properties: readable and writable, but they are not documented. Should we make them private, or expose them? I for one am in favor of making them documented public properties, but would like to hear what others think. Thanks.

@ronkorving ronkorving added doc Issues and PRs related to the documentations. net Issues and PRs related to the net subsystem. labels Jul 31, 2018
@ronkorving
Copy link
Contributor Author

Sorry, duplicate of #21431

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations. net Issues and PRs related to the net subsystem.
Projects
None yet
Development

No branches or pull requests

1 participant