lerkolabs/uptop
1
1
Fork 0
Code Issues 5 Pull Requests 1 Actions Packages Projects 1 Releases 1 Wiki Activity

feat(tui): two-column detail panel with type-specific enrichment #156

Merged
lerko merged 1 commits from feat/detail-panel-enrichment into main 2026-06-28 14:28:19 +00:00
Conversation 1 Commits 1 Files Changed 1
+223 -15
lerko commented 2026-06-28 14:23:58 +00:00
Owner
Copy Link
Copy Source

Issue #65 — detail panel enrichment.

Changes

Redesign inline detail panel from single left-aligned column to two-column layout:

  • Left (~55%): latency chart, min/avg/max, 30-day uptime timeline
  • Right (~45%): status summary, type-specific metadata, uptime/retries, state changes (up to 5, one per line with error reasons)

Type-specific metadata by monitor type:

  • HTTP: response code (colored by status) + SSL expiry days
  • Ping: hostname
  • Port: hostname:port
  • Push: interval + last heartbeat time
  • DNS: resolve type + server

Narrow terminals (<80 cols) fall back to original stacked layout.

Test plan

  • go build ./... — clean
  • go test ./... — all pass
  • golangci-lint run ./... — 0 issues
  • Visual verification via tui-review: two-column layout renders correctly on wide terminal
  • Ping monitor shows hostname in type line
  • State changes display vertically with error reasons
Issue #65 — detail panel enrichment. ## Changes Redesign inline detail panel from single left-aligned column to two-column layout: - **Left (~55%)**: latency chart, min/avg/max, 30-day uptime timeline - **Right (~45%)**: status summary, type-specific metadata, uptime/retries, state changes (up to 5, one per line with error reasons) Type-specific metadata by monitor type: - **HTTP**: response code (colored by status) + SSL expiry days - **Ping**: hostname - **Port**: hostname:port - **Push**: interval + last heartbeat time - **DNS**: resolve type + server Narrow terminals (<80 cols) fall back to original stacked layout. ## Test plan - [x] `go build ./...` — clean - [x] `go test ./...` — all pass - [x] `golangci-lint run ./...` — 0 issues - [x] Visual verification via tui-review: two-column layout renders correctly on wide terminal - [x] Ping monitor shows hostname in type line - [x] State changes display vertically with error reasons
lerko added 1 commit 2026-06-28 14:23:59 +00:00
feat(tui): two-column detail panel with type-specific enrichment
CI / test (pull_request) Successful in 1m52s
Details
CI / lint (pull_request) Successful in 1m17s
Details
CI / vulncheck (pull_request) Successful in 51s
Details
822eda4dfd 
Redesign the inline detail panel from a single left-aligned column
to a two-column layout that uses the full panel width.

Left column (55%): latency chart, min/avg/max stats, 30-day
uptime timeline.

Right column (45%): status/latency/last-check summary, type-
specific metadata (HTTP response code + SSL expiry, ping hostname,
port target, push interval/last heartbeat, DNS resolver), uptime
percentage + retry count, and up to 5 state changes listed
vertically with error reasons.

Narrow terminals (<80 cols) fall back to the original stacked
single-column layout.
lerko merged commit 822eda4dfd into main 2026-06-28 14:28:19 +00:00
lerko deleted branch feat/detail-panel-enrichment 2026-06-28 14:28:19 +00:00
lerko commented 2026-06-28 14:28:36 +00:00
Author
Owner
Copy Link
Copy Source

closes issue #65

closes issue #65
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working
 distribution
Packaging, publishing, branding
 feature
New functionality
 github
Forwarded from GitHub
 polish
UX/visual refinement
 refactor
Code quality, no behavior change
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lerko (Tyler Koenig)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lerkolabs/uptop#156
Delete Branch "feat/detail-panel-enrichment"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?