Do you know what happens if a request to connect to signalR takes longer than 10 seconds?

[labeled]

We're using your default reconnect policy and noticing sometimes that when a request to connect hangs for longer than 10 seconds it seems to get stuck in a forever loop trying to reconnect even though state shows the status as connected.
It might be that timer() queues up the next event before the first one has finished.

[Odonno]

ngrx-signalr-core/src/projects/ngrx-signalr-core/src/lib/effects.ts

Line 210 in 5cd4014

takeUntil(actions$.pipe(ofType(signalrConnected), ofHub(action)))

As per this line, the reconnect should abort when the hub finally connects. So if it does not, the reconnect effect is indeed stuck in a loop.

I don't see why it would still try to reconnect when the hub is connected. Is it possible for you to provide a reproduction repository?

[Odonno]

Per #37 issue and since v14.1.0, you can now use automatic reconnect provided by the @microsoft/signalr library. Check the readme file to see how it works.

[labeled]

Per #37 issue and since v14.1.0, you can now use automatic reconnect provided by the @microsoft/signalr library. Check the readme file to see how it works.

Thank you for this! We will more than likely start using that!