help wanted
Repository metrics
- Stars
- (19,563 stars)
- PR merge metrics
- (平均マージ 5d 16h) (30d で 138 merged PRs)
説明
Context: https://cube-js.slack.com/archives/CC0403RRR/p1642620249094800
When using the real-time websocket, there is no error handling available when the socket disconnects after the visual has been rendered. While the socket is disconnected, no new messages are published so rendered views will become stale without any error or update. Would like the ability to access the socket state (connected/connecting/error) as well as the last message to either handle errors in each visual, or render a general status component to show the health of the data on the screen.