Topology: tap to trace on phones, name cables into a patch panel #41

Merged
jared merged 1 commits from topology-polish into main 2026-11-14 22:22:48 -05:00
Owner

Two follow-ups to the topology page and power map (#39, #40).

Tap to trace on touch screens

Before this, a phone could not show power feed lines or the path to the internet, because both appeared only on hover.

  • The first tap on a device traces it: its path to the internet, plus the dotted feed lines to and from its outlets.
  • A second tap on the same device opens its page.
  • Tapping empty canvas clears the trace.
  • The trace stays through the 30 s refresh.
  • Mouse and keyboard behaviour is unchanged.

Cables into a patch panel

The cutsheet already records cable C01 from the gateway's port 8 to patch panel port 1. The page used to draw that end as "unknown device".

  • Each cutsheet cable now carries where its other end goes (cable.far: device, port, kind).
  • When an unknown device's cable is documented into a patch panel, its card shows the panel's 24 jacks, the cable lands on the documented jack, and the card is named "Patch panel port 1". The second line says the device beyond the panel is unknown.
  • A stub that already has a better name, such as POE port 1, keeps it and adds "via Patch panel port 2".
  • The cable panel's Cutsheet row shows where the far end goes ("into UACC-Rack-Panel-Patch-Blank-24 port 1").
  • A cable whose far end is a live device is unchanged.

Tests

  • Three new tests in test_topology.py:
    • an unknown device is named after the panel
    • a named stub keeps its name and gets via
    • a cable to a live device has no via
  • The cable label test now checks far.
  • Results: 474 passed; flake8 and bandit are clean; eslint is at the baseline of 21 warnings; no em or en dashes.
  • I checked the phone behaviour with Playwright touch taps:
    • one tap traces the RPDU and shows its 8 feed lines without navigating
    • a re-render keeps the trace
    • tapping empty canvas clears it
    • two taps open /device/RPDU

Screenshots (anonymised preview data)

Patch panel end and cable panel Phone, one tap on the RPDU

🤖 Generated with Claude Code

Two follow-ups to the topology page and power map (#39, #40). ## Tap to trace on touch screens Before this, a phone could not show power feed lines or the path to the internet, because both appeared only on hover. - The first tap on a device traces it: its path to the internet, plus the dotted feed lines to and from its outlets. - A second tap on the same device opens its page. - Tapping empty canvas clears the trace. - The trace stays through the 30 s refresh. - Mouse and keyboard behaviour is unchanged. ## Cables into a patch panel The cutsheet already records cable C01 from the gateway's port 8 to patch panel port 1. The page used to draw that end as "unknown device". - Each cutsheet cable now carries where its other end goes (`cable.far`: device, port, kind). - When an unknown device's cable is documented into a patch panel, its card shows the panel's 24 jacks, the cable lands on the documented jack, and the card is named "Patch panel port 1". The second line says the device beyond the panel is unknown. - A stub that already has a better name, such as POE port 1, keeps it and adds "via Patch panel port 2". - The cable panel's Cutsheet row shows where the far end goes ("into UACC-Rack-Panel-Patch-Blank-24 port 1"). - A cable whose far end is a live device is unchanged. ## Tests - Three new tests in `test_topology.py`: - an unknown device is named after the panel - a named stub keeps its name and gets `via` - a cable to a live device has no `via` - The cable label test now checks `far`. - Results: 474 passed; flake8 and bandit are clean; eslint is at the baseline of 21 warnings; no em or en dashes. - I checked the phone behaviour with Playwright touch taps: - one tap traces the RPDU and shows its 8 feed lines without navigating - a re-render keeps the trace - tapping empty canvas clears it - two taps open /device/RPDU ## Screenshots (anonymised preview data) | | | |---|---| | Patch panel end and cable panel ![](https://code.lotusguild.org/LotusGuild/gandalf/raw/branch/pr-41-screenshots/01-patch-panel.png) | Phone, one tap on the RPDU ![](https://code.lotusguild.org/LotusGuild/gandalf/raw/branch/pr-41-screenshots/02-phone-tap-trace.png) | 🤖 Generated with [Claude Code](https://claude.com/claude-code)
jared added 1 commit 2026-11-14 22:16:35 -05:00
Topology: tap to trace on phones, name cables into a patch panel
Lint / JS (eslint) (push) Successful in 19s
Lint / Python (flake8) (push) Successful in 1m20s
Lint / Notify on failure (push) Skipped
Lint / Deploy (push) Skipped
Lint / JS (eslint) (pull_request) Successful in 27s
Lint / Python (flake8) (pull_request) Successful in 1m46s
Lint / Notify on failure (pull_request) Skipped
Lint / Deploy (pull_request) Skipped
Security / Python Security (bandit) (pull_request) Successful in 1m9s
Test / Python Tests (pytest) (pull_request) Successful in 1m23s
Security / Python Security (bandit) (push) Successful in 1m10s
Test / Python Tests (pytest) (push) Successful in 1m18s
b9e008bc2b
- Touch screens have no hover, so the first tap on a device traces its path to
  the internet and its power feeds; a second tap opens it. Tapping empty canvas
  clears it, and the trace survives the 30 s refresh.
- A cutsheet cable now carries where its other end goes. An unknown device on a
  cable documented into a patch panel is drawn as that panel's jacks, named
  "Patch panel port N"; a named stub notes "via Patch panel port N". The cable
  panel shows the far end of the cutsheet cable.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jared scheduled this pull request to auto merge when all checks succeed 2026-11-14 22:22:41 -05:00
jared merged commit 206175df39 into main 2026-11-14 22:22:48 -05:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: LotusGuild/gandalf#41