Allow plugin "stateful" disconnection/exit. #36
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
connect()
method to control if client automatically callsprocess.exit(0)
upon socket error/close (default istrue
).hadError <boolean>
parameter passed on from socket's 'close' event (true
if the socket had a transmission error).err <Error>
parameter passed on from socket's 'error' event.disconnect()
method which closes any current connection withsocket.end()
.exit()
from multiple locations since socket's 'close' event is going to be fired regardless.Just to note, if the only thing keeping the Node process active is the open socket to TP, then the plugin/program will exit anyway once the socket is closed/errors, regardless of the new 'exitOnClose' option. The only thing this option controls is literally if
process.exit(0)
is called automatically upon disconnection (or lack of successful connection in the first place).