feat: searchable run history panel with status and latency#419
Open
shaunpatterson wants to merge 2 commits into
Open
feat: searchable run history panel with status and latency#419shaunpatterson wants to merge 2 commits into
shaunpatterson wants to merge 2 commits into
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Two UI fixes surfaced when the History button crowds the editor toolbar: - The toolbar used floats (.actions float left/right). When the right action group no longer fit beside Query/Mutate it dropped below, collapsing the float container into an empty band + a half-row of buttons. Switch .header/.actions to flexbox (flex-wrap, margin-left auto) so a crowded toolbar wraps into clean rows. - The history dropdown was position:absolute right:0 width:420px, anchored to the mid-toolbar History button — on a narrow editor pane it extended left off-screen and got clipped. Make it position:fixed with top/left/width computed from the button rect and clamped to the viewport, recomputed on resize, so it always stays visible. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
Author
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 History button in the editor toolbar opens a searchable panel of past runs (like Memgraph Lab's Run History), newest first. Each row shows:
react-timeago, already a dependency).A search input filters rows by case-insensitive substring; clicking a row loads that query into the editor and activates the frame (same dispatches the existing history strip uses). Closes on outside click and Escape; the active frame's row is highlighted.
Implementation notes
lib/runHistory.js(summarizeFrame,filterFrames,formatLatencyMs) — status prefers the JSON tab result and falls back to any completed tab, so a query run only on the Visual tab still shows green/red.RECEIVE_FRAMEnow stampscreatedAt(preserved if already present); legacy persisted frames without it fall back to the existingtimestampfield or omit the time.Testing
31 unit tests on the helpers (status across tab results, latency formatting, snippet truncation, filtering).
npm run buildpasses.🤖 Generated with Claude Code