[GH-ISSUE #5482] [Feature] Add CSV and TSV output for tabular analysis views #3335

New issue

Closed

opened 2026-10-31 00:39:17 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 00:39:17 +00:00

Owner

Originally created by @jayykernel on GitHub (Oct 20, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/5482

Problem

REA's JSON output is useful for automation, but users often need to inspect or compare tabular facts in a spreadsheet. Converting a simple inventory or selected analysis-view page currently requires an external script or manual transformation.

Proposed change

Add opt-in CSV and TSV formats for view kinds whose result is naturally row-oriented, such as artifact inventories and selected analysis-view collections. Keep JSON as the complete canonical format; do not flatten nested Evidence silently.

Acceptance criteria

Export only explicitly selected fields, with stable column order and documented handling of absent values.
Escape delimiters, quotes, newlines, and Unicode correctly.
Include a clear limitation/error when the requested view is not representable as rows.
Keep coverage, truncation, and pagination metadata available, either through documented sidecar metadata or a clearly specified output convention.
Add round-trip/escaping tests with empty, multiline, and non-ASCII values.

This is a usability enhancement, not a report of a current output defect.

Originally created by @jayykernel on GitHub (Oct 20, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/5482 ### Problem REA's JSON output is useful for automation, but users often need to inspect or compare tabular facts in a spreadsheet. Converting a simple inventory or selected analysis-view page currently requires an external script or manual transformation. ### Proposed change Add opt-in CSV and TSV formats for view kinds whose result is naturally row-oriented, such as artifact inventories and selected analysis-view collections. Keep JSON as the complete canonical format; do not flatten nested Evidence silently. ### Acceptance criteria - Export only explicitly selected fields, with stable column order and documented handling of absent values. - Escape delimiters, quotes, newlines, and Unicode correctly. - Include a clear limitation/error when the requested view is not representable as rows. - Keep coverage, truncation, and pagination metadata available, either through documented sidecar metadata or a clearly specified output convention. - Add round-trip/escaping tests with empty, multiline, and non-ASCII values. This is a usability enhancement, not a report of a current output defect.

bsakaguchi closed this issue

2026-10-31 00:39:17 +00:00

bsakaguchi referenced this issue

2026-10-31 01:09:10 +00:00

[PR #3460] [MERGED] fix(mcp): keep analyze_function progress strictly increasing #5751