Refactor connection indicator to patch with timestamp #11

ryan · 2026-03-03T20:25:11Z

ryan commented

2026-03-03 20:25:11 +00:00

Summary

Server patches ConnectionIndicator element with current timestamp on each heartbeat
Client-side JS checks every second if timestamp is stale (>20s)
Indicator turns red when stale, green when fresh
Properly detects connection loss (indicator turns red if no patches received)

Previously used Datastar signals which required the client to have a lastPing signal defined.

## Summary - Server patches `ConnectionIndicator` element with current timestamp on each heartbeat - Client-side JS checks every second if timestamp is stale (>20s) - Indicator turns red when stale, green when fresh - Properly detects connection loss (indicator turns red if no patches received) Previously used Datastar signals which required the client to have a `lastPing` signal defined.

ryan added 1 commit 2026-03-03 20:25:11 +00:00

refactor: patch connection indicator with timestamp

CI / Deploy / test (pull_request) Successful in 14s

Details

CI / Deploy / lint (pull_request) Successful in 26s

Details

CI / Deploy / deploy (pull_request) Has been skipped

Details

19c48d593a

Server patches the ConnectionIndicator element with a timestamp on
each heartbeat. Client-side JS checks every second if the timestamp
is stale (>20s) and toggles red/green accordingly.

This properly detects connection loss since the indicator will turn
red if no patches are received.

ryan force-pushed refactor/patch-connection-indicator from 19c48d593a to 06b3839c3a

2026-03-03 20:30:59 +00:00

Compare

ryan merged commit 589d1f09e8 into main

2026-03-03 20:32:11 +00:00

ryan referenced this issue from a commit

2026-03-03 20:32:13 +00:00

Merge pull request 'Refactor connection indicator to patch with timestamp' (#11) from refactor/patch-connection-indicator into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: ryan/games#11