Allow custom app logic to trigger when a websocket connects/reconnects #75
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.
When using an ephemeral WebSocket to listen for completion of a FireFly action, you need to know the socket is connected before you submit the action. This isn't currently possible in the SDK.
It's also not possible to send custom commands over the WebSocket, or trigger other processing as a side-effect of a reconnect.
Also in unit tests in a framework like Jest, you cannot allow a test to write log statements after the test exits (see jestjs/jest#9324 (comment)).
This drives a requirement for a
close()function that allows us to await the logging of the close, which is also included as an option in this PR.