Closed vicary closed 2 weeks ago
canary
)The latest changes of this PR are available as canary on npm (based on the declared changesets ): |
Package | Version | Info |
---|---|---|---|
@gqty/cli |
4.2.1-canary-20241110205308.6f5123252e0573c9ed6a8616c6d0a9d99f18707b |
npm ↗︎ unpkg ↗︎ | |
gqty |
3.2.2-canary-20241110205308.6f5123252e0573c9ed6a8616c6d0a9d99f18707b |
npm ↗︎ unpkg ↗︎ | |
@gqty/logger |
3.0.5-canary-20241110205308.6f5123252e0573c9ed6a8616c6d0a9d99f18707b |
npm ↗︎ unpkg ↗︎ | |
@gqty/react |
3.0.5-canary-20241110205308.6f5123252e0573c9ed6a8616c6d0a9d99f18707b |
npm ↗︎ unpkg ↗︎ | |
@gqty/solid |
0.2.2-canary-20241110205308.6f5123252e0573c9ed6a8616c6d0a9d99f18707b |
npm ↗︎ unpkg ↗︎ |
Summary
The
onSubscribe
option on the core APIsubscribe()
is firing only on the firstconnection_ack
, callbacks on subsequent subscriptions using the same WebSocket connection are unintentionally skipped.Expected Result
onSubscribe
is called when we receiveconnection_ack
.onSubscribe
is called immediately.onSubscribe
is called when the connection is established.