Repository navigation
Beacon table: fixed-width aligned columns, strongest signal on top - #7
Merged
jappeace merged 5 commits intoJul 14, 2026
Merged
Conversation
- Columns: serial (the MAC's low three hex bytes, the same digits factory names carry, so renamed beacons show a stable serial too), bare RSSI, bare battery, the device's rate, and status. Each cell is its own node, colored by the rate verdict; a header row labels the columns. - The rate column shows the exact period once the beacon was configured, the measured estimate (tilde) while only observed, and "?" until a second advertisement gives a measurement. - Rows sort by RSSI, strongest on top (sabotage-verified: insertion order fails the new sort test). Prompt: okay this is better, can you make an actual table out of it, show just the serial number (no kbeaconpro prefix), rssi (just number), battery (just number), and th econfigured ping rate (not shown currently), and can you make it a table?, sort highest rssi on top Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Review gate finding: inserting weak-then-strong made the prepend accumulator coincidentally sorted, so dropping the sort entirely passed. Three beacons inserted middle, strong, weak make the raw list, its reverse, and only the RSSI sort distinguishable; both the no-sort and reverse mutants now fail the test (verified). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
hatter #246 adds the fixed-width style property #245 asked for; the serial, RSSI, battery and rate columns share fixed widths between the header and every row (the status column stays content-sized), and the " | " separators go away. A new test walks the rendered widths and asserts each row's columns equal the header's. Pin moves to the hatter PR branch; repoint after #246 merges. Prompt: just go implement this too if you need it for my request: jappeace/hatter#245 the point of this ota app is alos to sorta fuzz hatter for obviously missing features Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The wsWidth style property landed on jappeace/hatter master, so the pin moves off the jappeace-sloth feature branch. All 67 tests pass against the new pin. Prompt: okay merged the hatter one Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
The table work that landed on this branch after #6 merged (its commits were orphaned by the merge timing; this PR carries them):
~estimatewhile observed,?before a measurement) and status.wsWidth(Add wsWidth: a fixed-width style property through all bridges hatter#246, resolving #245, built for this feature); a test walks the rendered widths and asserts each row's columns equal the header's.Pins hatter at the #246 branch head; repoint to master after #246 merges. Merge order: hatter#246, then this.
🤖 Generated with Claude Code