Does not reconnect if first connection failed

[gcoda]

I suspect this should be handled by @microsoft/signalr package.
But it does not even try to reconnect if connection.start() failed.

is it ok to reuse "private" function from ConnectionHub object inside createService -> init() -> catch { ... here ... }

something like this gcoda@980329e

[IlCallo]

I wouldn't call init function recursively and I'd use one of the existing packages for exponential backoff retry management

This means the "happy path" of the init function should be extracted to its own private function, let's call it connectAndProcessActions, which throws in case of a failed connection

Then init would use connectAndProcessActions applying the exponential backoff pattern and only executing the failFn if the max number of retries is reached

Also, I'd properly manage TS to avoid the connection as any casting and the //@ts-ignore
If you definitely need that, at least use //@ts-expect-error instead

If you wanna apply these fixes and send a PR, I can review it

Otherwise, if you use this into a commercial project, please check out our sponsorship page to get issue prioritization: github.com/sponsors/dreamonkey/sponsorships?tier_id=135990

[IlCallo]

This is a quick example on how to implement an exponential backoff retry pattern: vuejs/apollo@b17817e

[gcoda]

Then init would use connectAndProcessActions applying the exponential backoff pattern and only executing the failFn if the max number of retries is reached

i wanted to reuse reconnect function provided and supported by ConnectionHubBuilder, it is a bit weird to write two different reconnect retry handlers, one for initial connect and another for broken connection, maybe i should just modify .start() function in HubConnection\IConnection from ConnectionHubBuilder object instead