Retain fetch, decode, and parser detail in edit-open flows #637

New issue

Closed

opened 2026-05-06 19:55:42 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-05-06 19:55:42 +00:00

Owner

Parent: #634

Problem

PR and issue edit-open flows fetch details, decode JSON, and parse backend payloads before opening compose buffers. Fetch failures and parser failures are currently collapsed into broad messages such as failed to parse PR details, losing the decode/parser reason and any useful command output.

Scope

Improve failure messages in the load_details path.
Distinguish command failure, JSON decode failure, and backend parser failure.
Preserve bounded diagnostic details without exposing raw Lua tracebacks in normal UI.
Add tests for invalid JSON and parser exceptions.

Non-goals

Do not fix unrelated backend parser bugs in this issue.
Do not redesign compose buffers.

Parent: #634 ## Problem PR and issue edit-open flows fetch details, decode JSON, and parse backend payloads before opening compose buffers. Fetch failures and parser failures are currently collapsed into broad messages such as `failed to parse PR details`, losing the decode/parser reason and any useful command output. ## Scope - Improve failure messages in the `load_details` path. - Distinguish command failure, JSON decode failure, and backend parser failure. - Preserve bounded diagnostic details without exposing raw Lua tracebacks in normal UI. - Add tests for invalid JSON and parser exceptions. ## Non-goals - Do not fix unrelated backend parser bugs in this issue. - Do not redesign compose buffers.

barrettruth added the

bug

v0.2.0

labels

2026-05-06 19:55:42 +00:00

barrettruth referenced this issue

2026-05-06 19:56:06 +00:00

Tracker: error handling and edge cases #634

barrettruth referenced this issue from a pull request that will close it,

2026-05-06 21:26:15 +00:00

Retain edit-open failure details #649

barrettruth closed this issue