[Luyii]

What's new

API Table Viewer v1.5.0 extends response inspection into field-level debugging. Double-click a scalar in a table, tree or JSON viewer, enter a test value, then query or refresh the page to validate the result.

• Edit in place with Enter / blur to commit and Esc to cancel.
• Highlight changed values and provide a change list, field navigation, per-field restore and a single exit action.
• Keep mock rules across refreshes, cleared capture lists and reopened DevTools, scoped to the inspected tab and page origin.
• Apply patches to real Fetch / asynchronous XHR responses while keeping untouched fields current. Backend requests still execute.

Implementation

• Store field paths, types, values and stable array-row identifiers instead of a complete response draft.
• Restore session rules through document-start MAIN-world hooks and an isolated bridge before startup requests proceed.
• Resolve object-array rows by unique identifiers; skip invalid paths, ambiguous identifiers and changed types.
• Preserve unsafe integer literals through the shared codec. Responses over 1 MiB can be edited through small scalar patches; the existing 20 MiB capture limit remains.
• Add Chrome 114+, HTTP / HTTPS host access and session storage declarations. The earlier whole-response engine remains hidden as a regression baseline.

Project presentation

Rewrite the README around the new debugging workflow, with capability tables, an architecture diagram, CI status and documented limits. Add dedicated v1.5.0 release notes and update usage, architecture and installation guidance.

Validation

Local checks passed:

• 88 regression tests and extension resource / CSP / script checks.
• 8 HTTP / Worker subcases.
• 13 field-mocking tests, 18 earlier response-engine tests and 3 preview checks.
• ZIP whitelist, integrity, source-byte consistency and extracted-resource validation.
• Actual panel and Worker exercised in a simulated DOM for edits, cancellation, markers, restore and exit.

Chrome APIs and XHR are simulated in automated tests. Real Chrome installation, startup timing and application rendering still require the documented manual checks. GitHub Actions results are reported separately by this PR.