Repository navigation
Conversation
A console screen that draws each open case as one square in its workflow's band, coloured by state (needs you, stuck, running, near its limit, paused, on hold, waiting), under a strip of slots in use against the cap and cases closed today. Pointing at a square reads it; clicking selects it into a panel that opens the case. The bands scroll inside the view while the strip and filters stay put. GET /api/fleet-wall validates its answer against FleetWallPayload in core/monitor/models.py, and the console's types are generated from it. The read itself is not implemented: the route answers 501 and the screen shows its error state, except in demo mode, where it serves the seeded sample in core/monitor/fixtures.py. Taken from krmayankb/vigil PR #7 (fleet/console-monitor). Co-authored-by: krmayankb <krmayankb@gmail.com> Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Signed-off-by: gray <egboluche.g@gmail.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.
What
A Fleet Wall console screen (nav: Overview → Fleet Wall). It draws every open case as one square in its workflow's band.
The API is a contract, not an implementation
GET /api/fleet-wallis defined byFleetWallPayloadincore/monitor/models.py:schema.d.tsis generated from it, and the console's types alias it.The read itself (
core/monitor/wall.py) is not implemented:core/monitor/fixtures.py). That sample is also built from the models, so it cannot drift from the contract.The read's docstring lists each field's source and the TODOs for whoever implements it, e.g. index the run-by-case lookup before polling it every 10 s.
Tests
tests/unit/monitor/: 501 when unbuilt, demo fixtures satisfy the contract, a read that drops a field or sends an unknown state is refused, plus the level and time helpers.monitor.test.tsx: the wall draws, filters, selects and opens a case.SocConsole.test.tsx: nav order and separators.main.Origin
Taken from @krmayankb's krmayankb/vigil PR #7 (
fleet/console-monitor), credited as co-author. The data reads are left as 501 stubs, and the screen gained more of the design (states, hover readout, band slots, scrolling bands).Pulse is the follow-up PR, stacked on this one.