feat(issue): expose per-link direction and verb in inspect --json #96

Merged

Claude-Run merged 1 commit from feat/YT-40-link-direction-json into main

2026-07-03 17:58:51 +02:00

Claude-Run commented

2026-07-03 17:57:49 +02:00

Member

yt issue inspect --json returned two structurally identical entries for the two directed slots of a link type (they differed only by their issues array), so a consumer could not tell the blocker (depends on) from the blocked (is required for) without inverting silently.

Request direction on the inspect_issue links fetch, guarantee a direction (OUTWARD/INWARD/BOTH) on every serialized links[] entry, and attach a resolved verb (sourceToTarget for OUTWARD/BOTH, targetToSource for INWARD) computed client-side via IssueLink::resolve_verb. The linkType object and issues array (with idReadable and the nullable resolved stamp) are unchanged for back-compat. Documented on the yt issue inspect --json CLI help.

#YT-40

`yt issue inspect --json` returned two structurally identical entries for the two directed slots of a link type (they differed only by their `issues` array), so a consumer could not tell the blocker (`depends on`) from the blocked (`is required for`) without inverting silently. Request `direction` on the `inspect_issue` links fetch, guarantee a `direction` (`OUTWARD`/`INWARD`/`BOTH`) on every serialized `links[]` entry, and attach a resolved `verb` (`sourceToTarget` for `OUTWARD`/`BOTH`, `targetToSource` for `INWARD`) computed client-side via `IssueLink::resolve_verb`. The `linkType` object and `issues` array (with `idReadable` and the nullable `resolved` stamp) are unchanged for back-compat. Documented on the `yt issue inspect --json` CLI help. #YT-40

Claude-Run added 1 commit

2026-07-03 17:57:49 +02:00

feat(issue): expose per-link direction and verb in inspect --json

Check / fmt + clippy + build + tests (pull_request) Successful in 38s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

6cbd0f82e2

`yt issue inspect --json` returned two structurally identical entries for the two directed slots of a link type (they differed only by their `issues` array), so a consumer could not tell the blocker (`depends on`) from the blocked (`is required for`) without inverting silently.

Request `direction` on the `inspect_issue` links fetch, guarantee a `direction` (`OUTWARD`/`INWARD`/`BOTH`) on every serialized `links[]` entry, and attach a resolved `verb` (`sourceToTarget` for `OUTWARD`/`BOTH`, `targetToSource` for `INWARD`) computed client-side via `IssueLink::resolve_verb`. The `linkType` object and `issues` array (with `idReadable` and the nullable `resolved` stamp) are unchanged for back-compat. Documented on the `yt issue inspect --json` CLI help.

#YT-40