Say PoE on the run that carries it - #83
Merged
Merged
Conversation
Drawn as two links, PoE put two rows on the cable schedule where one
lead exists, with a duplicate-connection warning on top. Somebody loads
the van from that. Written as `poe over lan` it came out clean but named
the run PoE, and the network vanished from the drawing and the legend.
Neither says what is true: one Cat lead, carrying both.
sw.LAN1 <-> cam.LAN : lan 30m "N-01" [poe]
One run, one row. The drawing shows PoE beside the number and the
length; the schedule gains a 給電 column, and a show with no PoE in it
never grows one. It answers what gets asked on site — which ports have
to be PoE, and which boxes need no power supply.
A run that is not Cat is reported; nothing puts power down a coax. The
carrier decides it as everywhere else, so `ndi over lan [poe]` is fine.
An attribute with no value is a flag now. There is nothing to put on the
other side of an `=` that reads better than saying it once.
The column needed a word of its own: a `true` used to print as
"undeclared", which belongs to a device nobody declared and says the
opposite here.
The `poe` signal type is untouched, so nothing already written stops
working. Having both a type and a flag for one thing is a seam, and the
changeset says so rather than leaving it for somebody to find.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01824X53UWBk8JUvTPoN7hnu
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was wrong with the two ways it could be written
Two links —
duplicate-connection, and two rows on the cable schedule where one lead exists. Somebody loads the van from that.poe over lan— clean, one row, but the run is named PoE and the network disappears from the drawing and the legend.Neither says what is true: one Cat lead, carrying both. So PoE is a property of the run, not a run of its own.
What it buys
The questions that get asked on site: which ports have to be PoE, and which boxes need no power supply. Neither was readable before.
ndi over lan [poe]is fine.Two things fell out
An attribute with no value is a flag.
[poe]means[poe=true]. There is nothing to put on the other side of an=that reads better than saying it once.The column needed a word of its own. A
trueprinted as未宣言— that word belongs to a device nobody declared, and it says the opposite here. Columns now carry what theirtruemeans; the old one keeps the old default.Named rather than hidden
The
poesignal type is untouched, so nothing already written stops working. Having both a type and a flag for one thing is a seam. The changeset says so rather than leaving it for somebody to find.392 core tests, seven of them new; full CI locally.
🤖 Generated with Claude Code
https://claude.ai/code/session_01824X53UWBk8JUvTPoN7hnu