Skip to content

Create developer dashboard — event browser UI #376

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kenkenseb wants to merge 3 commits into
base: dev
Choose a base branch
from
Open

Create developer dashboard — event browser UI #376

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9f3881a
Create developer dashboard — event browser UI
kenkenseb Jul 29, 2026
3355c21
Update developer dashboard — event browser UI
kenkenseb Jul 31, 2026
67cc80f
Update developer dashboard — event browser UI
kenkenseb Jul 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions developer dashboard — event browser UI
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
https://www.figma.com/design/OhOGPhmbRZM9rlYWENffXf/Untitled?node-id=0-1&t=UWpCsnybapHNpwFz-1

@Depo-dev Depo-dev Jul 31, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR adds a single file containing one Figma URL and no code, but the description and title present it as an implemented dashboard (real-time event feed, slide-over JSON drawer, donut gauge for ledger lag, API key management). None of that exists in this diff.

Three concrete problems:

  1. Closes #76 would auto-close an unimplemented feature. Issue feat(infra): developer dashboard — event browser UI #76 (feat(infra): developer dashboard — event browser UI) is still open and unbuilt. Merging this closes it while shipping nothing, which silently corrupts the backlog.

  2. The file itself shouldn't be committed. The filename has spaces and an em-dash with no extension (developer dashboard — event browser UI). That breaks shell globbing and tooling on most platforms, and a bare URL in a repo file goes stale the moment the Figma doc moves.

  3. A Figma link isn't reviewable as code. There's nothing here to check for correctness, accessibility, or integration with the existing stack.

The design work itself may well be good — the problem is purely the delivery channel. Please close this PR and post the Figma link as a comment on #76 instead, keeping the issue open. If the intent is to actually build the dashboard, open a fresh PR with the implementation and link the design from the description.

Worth flagging: there's currently no accepted home for design deliverables in this repo, which is probably why this landed as a PR. That's on us, not you — I've logged it as a gap to fix.