tls: secureConnect event will not be emitted if TLSSocket is created via constructor instead of tls.connect

[nbdd0121]

• Version: 7.3
• Platform: Any
• Subsystem: Any

In current TLS doc, secureConnect is documented as an event of TLSSocket. However, the event will only be emitted if the socket is created via tls.connect. Basically there is no sensible event to listen on for the 'connect' event if the socket is created directly via new tls.TLSSocket.

[sam-github]

Confirmed. I will document.

[sam-github]

PTAL at #10846

[Trott]

@sam-github Should this issue remain open?

[sam-github]

Yes, our documentation is incorrect, and parts of the TLS API are unuseable now (at least, not useable with documented methods and events). I tried to fix, but #10846 was rejected.

[BridgeAR]

I guess #10846 would be a good starting point to fix this. It was just closed due to being stalled and did not get rejected.