Skip to content

fix: stop the Details tab repeating what the page header already says - #69

Merged
FMSMITH91 merged 1 commit into
mainfrom
fix/trim-duplicated-details-rows
Aug 9, 2026
Merged

fix: stop the Details tab repeating what the page header already says#69
FMSMITH91 merged 1 commit into
mainfrom
fix/trim-duplicated-details-rows

Conversation

@FMSMITH91

Copy link
Copy Markdown
Owner

"Installed: Yes" could never say anything elseserver_detail redirects a server that's still installing, so the row was pure decoration. Pulling that thread, most of the card turned out to be a second copy of the header:

row already shown as
Name the <h1> two inches above
Game Type header subtitle
Port header subtitle
Status the header badge
Installed always Yes, see above

Status was worse than redundant. The header badge is the one the poll keeps current; the table's copy was rendered once and never updated, so it went stale the moment the server changed state while you were looking at it.

What's left is what you can't read anywhere else — the three switches, plus Short Name only when it differs from the display name, which is the case actually worth surfacing (a custom-named instance whose Linux user is something else). The card is titled Server Settings now, because that's what it is.

Same pattern in the Host card

Public IP: 147.135.70.122 sat directly above Connect: 147.135.70.122:28960. The Connect row is the same address plus the port and the one you can click to copy. Public IP now appears only while the address is still resolving, where resolving… is real information.

Measured, not guessed

Counting occurrences in a rendered page:

value before after
public IP 2 1
Status 2 1
Game Type / Installed 1 0
Port 2 2 — correctly: metadata, and inside the copyable connect string

unit 839 · smoke 300 · rbac 65 · template_actions 7 · lint clean.

🤖 Generated with Claude Code

"Installed: Yes" could never say anything else — server_detail redirects a
server that is still installing, so the row was decoration. Pulling that
thread, most of the card was a second copy of the header:

  Name        the <h1> two inches above it
  Game Type   header subtitle
  Port        header subtitle
  Status      the header badge — and worse, the badge is the one the poll
              keeps current, so this copy went STALE the moment the server
              changed state while you were looking at it
  Installed   always Yes, see above

What is left is what you cannot read anywhere else: the three switches, plus
Short Name — and that only when it differs from the display name, which is
the case worth pointing out (a custom-named instance whose Linux user is
something else). The card is titled Server Settings now, because that is what
it is.

Same thing in the Host card: "Public IP: 147.135.70.122" sat directly above
"Connect: 147.135.70.122:28960". The Connect row is the same address plus the
port AND the one you can click to copy, so Public IP now appears only while
the address is still resolving, where "resolving…" is real information.

Measured on a rendered page: the public IP went from appearing twice to once,
Status from twice to once, Installed and Game Type from once to not at all.
Port still appears twice and should — once as metadata, once inside the
copyable connect string.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@codacy-production

codacy-production Bot commented Aug 9, 2026

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Coverage ∅ diff coverage · +0.03% coverage variation

Metric Results
Coverage variation +0.03% coverage variation (-1.00%)
Diff coverage diff coverage

View coverage diff in Codacy

Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (ee31427) 11957 5802 48.52%
Head commit (1e44375) 11957 (+0) 5806 (+4) 48.56% (+0.03%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#69) 0 0 ∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@FMSMITH91
FMSMITH91 merged commit b1ec072 into main Aug 9, 2026
19 checks passed
@FMSMITH91
FMSMITH91 deleted the fix/trim-duplicated-details-rows branch August 9, 2026 03:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant