Description
When Provider tries re-connecting after a disconnection, if there is an error connecting and max tries are reached, no programatic way to tell this is finished and take additional action.
The rejection promise is not being handled or sent outside of the provider in anyway.
Steps to reproduce the bug
Steps to reproduce the behavior:
- Be using HP Provider
- Go offline (Turn WIFI off)
- Come back online (Turn WIFI on)
- HP Provider tries to re-connect
- After max amount rejection promise is swallowed and user not able to determine retry is over
Expected behavior
There is some how access to promise rejection of connect so user knows when retries are over and can take additional action
Screenshot, video, or GIF
This is the code where connect is called and rejection promise not handled:
Environment?
- operating system: Mac
- browser: Chrome
- mobile/desktop: Desktop
- hocuspocus version: Provider 1.0.0
Description
When Provider tries re-connecting after a disconnection, if there is an error connecting and max tries are reached, no programatic way to tell this is finished and take additional action.
The rejection promise is not being handled or sent outside of the provider in anyway.
Steps to reproduce the bug
Steps to reproduce the behavior:
Expected behavior
There is some how access to promise rejection of connect so user knows when retries are over and can take additional action
Screenshot, video, or GIF
This is the code where connect is called and rejection promise not handled:
hocuspocus/packages/provider/src/HocuspocusProvider.ts
Line 616 in 476898b
Environment?