Handle nullable Gitea issue metadata in context endpoint #50

Closed
opened 2026-08-05 23:16:49 +00:00 by rockachopa · 0 comments
Member

Evidence

Gitea issue responses can contain labels: null or assignees: null (observed while fetching this repository's closed issues). The context endpoint currently iterates i.get("labels", []) and i.get("assignees", []); when either key exists with a null value, /api/v1/context raises TypeError instead of rendering the issue.

Expected behavior

Normalize nullable issue collections to empty lists so the context endpoint continues returning the affected issue with labels: [] and assignees: []. Add a behavioral regression test.

## Evidence Gitea issue responses can contain `labels: null` or `assignees: null` (observed while fetching this repository's closed issues). The context endpoint currently iterates `i.get("labels", [])` and `i.get("assignees", [])`; when either key exists with a null value, `/api/v1/context` raises `TypeError` instead of rendering the issue. ## Expected behavior Normalize nullable issue collections to empty lists so the context endpoint continues returning the affected issue with `labels: []` and `assignees: []`. Add a behavioral regression test.
timmy was assigned by rockachopa 2026-08-05 23:16:49 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#50
No description provided.