WebSocketClient should propagate ConnectionClosedError after max_reconnects #818
Description
Currently it silently just ends after max reconnects is exceeded, instead of return it should raise the ConnectionClosedError.
{{ message }}
Currently it silently just ends after max reconnects is exceeded, instead of return it should raise the ConnectionClosedError.