Skip to content

Show users the real v0.2.0 workbench #13

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

Merged
achieve0410 merged 1 commit into from
Jul 28, 2026
Merged

Show users the real v0.2.0 workbench #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 9 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,15 @@ remain stable compatibility identifiers in `v0.2.x`.
It binds the UI/API to loopback HTTPS. It does not contact production services,
databases, or external URLs, and it has no telemetry or export path.

## Demo

[![code-debugger v0.2.0 showing Routes, an expanded orders execution graph, Flow Outline, and Evidence Inspector for the synthetic Nuxt and Django fixture](https://github.com/achieve0410/code-debugger/releases/download/v0.2.0/code-debugger-v0.2.0-demo.png)](https://github.com/achieve0410/code-debugger/releases/download/v0.2.0/code-debugger-v0.2.0-demo.png)

*Actual `v0.2.0` workbench using only synthetic `fixtures/nuxt-django` data.
Select **Analyze**, choose `/orders`, and use **Expand all** to reveal the
frontend-to-Django flow. Select any node or edge to inspect its bounded evidence
on the right. Click the image for the full-size view.*

## What it shows

For the synthetic Nuxt/Django fixture, selecting `/orders` exposes a bounded
Expand Down