I don't know why, but clearing the interval doesn't work right for me. You can notice this if you add a log of connectionRetryUpdateInterval into the interval. There are much more handles created than it should. On long term, this could be a performance killer. If you trigger click #connection-try-reconnect then many new intervals are also created.
The code is very short and simple, but I really don't get it. It makes me want to tear my hair out!
i see what you are talking about - modified the package to prevent multiple intervals from being created - deployed a new version of the package (0.3.0) - let me know if that does not fix your issue
I don't know why, but clearing the interval doesn't work right for me. You can notice this if you add a log of
connectionRetryUpdateInterval
into the interval. There are much more handles created than it should. On long term, this could be a performance killer. If you triggerclick #connection-try-reconnect
then many new intervals are also created. The code is very short and simple, but I really don't get it. It makes me want to tear my hair out!