Skip to content

fix(issues): return [] not null for empty issues list and events#90

Merged
Palash Shah (Palashio) merged 1 commit into
mainfrom
fix/issues-null-empty-array
Apr 30, 2026
Merged

fix(issues): return [] not null for empty issues list and events#90
Palash Shah (Palashio) merged 1 commit into
mainfrom
fix/issues-null-empty-array

Conversation

@Palashio
Copy link
Copy Markdown
Contributor

Summary

`issues list` and `issues events` both used `var data []map[string]any`, which stays nil when the API returns zero results. `json.Marshal(nil)` serializes to `null` instead of `[]`, breaking any caller that tries to iterate or check the length of the result.

The issues agent calls `langsmith project issues events --look-back-minutes 360` on every cron scan. For projects with no recent activity this returns `null`, which the agent can't handle cleanly.

Fix: initialize as `data := []map[string]any{}` in both commands so empty results always serialize to `[]`.

Test Plan

  • All tests pass
  • Verified the pattern: zero-event projects now return `[]` not `null`

Release Note

Fix `issues list` and `issues events` returning `null` instead of `[]` when there are no results.

Both `issues list` and `issues events` used `var data []map[string]any`
which stays nil when no results are returned, serializing to JSON null
instead of []. Callers (including the issues agent) cannot iterate null.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@Palashio Palash Shah (Palashio) merged commit cb0b127 into main Apr 30, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants