Issue #, if available:
add websocket onClose callback
Description of changes:
Currently, when websocket connection is closed, onClose is called but is not exposed from ChatJs.
We only expose onConnectionLost which is fired if both primary and secondary websocket connection has been closed.
Customer also wants to listed to onClose event so they can immidiately start polling for getTranscript.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Issue #, if available: add websocket onClose callback
Description of changes: Currently, when websocket connection is closed,
onCloseis called but is not exposed from ChatJs. We only exposeonConnectionLostwhich is fired if both primary and secondary websocket connection has been closed.Customer also wants to listed to
onCloseevent so they can immidiately start polling forgetTranscript.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.