On error event is only fired after connection is restored

[cgvalayev]

Steps to reproduce:

1. Chrome dev tools "Network conditions -> Offline" - we get nothing from the graphql client on.error, on.closed
2. "Network conditions -> No throttling" - on.error fires

Also, I am having a hard time understanding when the client is trying to retry and how many attempts left.

Use cases:

1. I would like to be able to display connectivity warning in my app, should I be using something else?
2. What is the best way to handle reconnection after all attempts were exceeded, for example user left computer for 2 days and came back? - answered here Best practice for reconnecting after retryAttempts has been passed? #121

[enisdenjo]

on.error and on.closed are hooked up directly to the browsers WebSocket implementation, see here:

graphql-ws/src/client.ts

Lines 665 to 666 in 48e7bd9

	socket.onerror = (err) => emitter.emit('error', err);
	socket.onclose = (event) => emitter.emit('closed', event);

If playing with network throttling does not yield the expected results, I reckon it's due to some browser thing. You can confirm this by using the WebSocket directly.

Also, I am having a hard time understanding when the client is trying to retry and how many attempts left.

The retryAttempts client option controls the amount of retries and has the details answering your question. Furthermore, also read about the shouldRetry client option.

I would like to be able to display connectivity warning in my app, should I be using something else?

1. on.connecting indicates that the connection process to the server has started
2. on.connected indicates that the client has opened a WebSocket connection and that the server acknowledged
3. on.closed indicates that the WebSocket connection has closed, for whatever reason