Repository navigation
feat(acme): add an inspector tab for vendor calls - #10
Merged
Merged
Conversation
added 4 commits
November 3, 2026 22:39
A reset clears the recording but IDs keep counting, so an inspector polling with since could not tell its list was stale. Count the clears and return the count with the events.
The inspector's audience should follow the feed without reading vendor paths. Map each call the lender makes to one sentence, and fall back to the raw method and path for a call the table does not know.
A presenter needs to show what the lender asks Stripe, Plaid and Xero while the demo runs. Poll the recorder, show each call with its caption, source and bodies, filter by vendor, and start over after a reset. The demo header opens it in a second tab.
Presenters need to know the second tab exists, what each row means, and that a reset empties it.
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.
Motivation
A presenter needs to show what the lender asks Stripe, Plaid and Xero while the demo runs. The recorder already keeps every call, bodies included, with credentials masked. This adds the page that shows them.
Changes
feat(shared): the recorder counts how many times it was cleared, and/api/eventsreturns the count asgeneration. A reset clears the recording but IDs keep counting, so without it an inspector could not tell its list was stale.feat(web): a plain-language caption for each call the lender makes. An unknown call shows its method and path.feat(web): an/inspectorroute and an Open inspector button in the demo header. Newest call first, with vendor, who served the app emulator, status, duration, request and response bodies (JSON laid out for reading), a vendor filter, and an empty list after a reset.docs(acme): the inspector section of the Usage Guide.Known limits: seed calls are not shown (seeding does not go through the recorder), there is no per-vendor "what it holds" panel, and the base URL switcher is not built. Reading sales is paged, so a run shows dozens of Stripe calls.
Tests
Tests were shown to fail without the change: with the generation count removed, the recorder and API tests fail, and with the reset handling removed, the inspector's reset test fails.
Live run in Chrome against Stripe, Plaid and Xero app emulators built from
WonderTwin-AI/wondertwinorigin/main (8e4a7235), demo and inspector in two tabs: one full run showed 28 calls with captions, the vendor filter worked, a row opened to its bodies, the bank account number showed as[redacted], Reset emptied the inspector from the other tab, a second run filled it again, and the console was clean.Related
Follows
localstack-samples/localstack-app-emulators#7andlocalstack-samples/localstack-app-emulators#9.