When a list command returns zero items, applying a jq filter (e.g., --jq '.') outputs null instead of []. Without --jq, the output is correctly [].

Root cause: Go's json.Marshal encodes nil slices as null, not []. SDK list responses use nil slices for empty results. segmentio/cli's printer handles nil typed slices as [] directly, bypassing json.Marshal — so the discrepancy only surfaces through the jq code path.

Changes

• internal/cmd/output/jq/jq.go: Add marshalForJQ helper that uses reflection to detect nil slices and encode them as [] before jq processing. ApplyToRaw now calls this instead of json.Marshal directly.

func marshalForJQ(v any) ([]byte, error) {
    if v != nil {
        rv := reflect.ValueOf(v)
        if rv.Kind() == reflect.Slice && rv.IsNil() {
            return []byte("[]"), nil
        }
    }
    return json.Marshal(v)
}

• internal/cmd/output/jq/jq_test.go: Add tests for nil-slice and empty-slice identity filter cases.

• Fixes Bug: Embedded jq parser does not handle empty arrays as expected #456

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.