Violation of the RTN4h spec

Open maratal opened this issue 2 years ago • 1 comments

It emits an UPDATE ConnectionEvent for changes to connection conditions for which the ConnectionState (e.g. CONNECTED) does not change. (The library must never emit a ConnectionState ConnectionEvent for a state equal to the previous state).

This only implemented for CONNECTED. Would be useful at the very least to implement it for CONNECTING as well. Now if you call connect twice, the transition CONNECTING -> CONNECTING will take place.

┆Issue is synchronized with this Jira Task by Unito

Oct 08 '23 20:10 maratal

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-3895

Oct 08 '23 20:10 sync-by-unito[bot]