Skip to content
Permalink
Browse files

doc: clarify timing of socket.connecting

Fixes: #25328

PR-URL: #25333
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
  • Loading branch information...
sam-github authored and addaleax committed Jan 4, 2019
1 parent e9b4d24 commit f3d86391d94b45c6276a87092c7fe2320ca13bd9
Showing with 5 additions and 4 deletions.
  1. +5 −4 doc/api/net.md
@@ -666,11 +666,12 @@ added: v6.1.0
-->
If `true`,
[`socket.connect(options[, connectListener])`][`socket.connect(options)`] was
called and has not yet finished. It will stay `true` until the socket becomes
connected, then it is set to `false` and the `'connect'` event is emitted. Note
that the
[`socket.connect(options[, connectListener])`][`socket.connect(options)`]
was called and has not yet finished. Will be set to `true` before emitting
`'connect'` event and/or calling
[`socket.connect(options[, connectListener])`][`socket.connect(options)`]'s
callback.
callback is a listener for the `'connect'` event.
### socket.destroy([exception])
<!-- YAML

0 comments on commit f3d8639

Please sign in to comment.
You can’t perform that action at this time.