[G1-04] Keep clean text output compact #50

Open
opened 2026-05-28 01:15:57 +02:00 by codex · 0 comments
Collaborator

Suggested executor: Gemini 3.5 Flash.

Wave: G1 — Text Output UX

Goal

Ensure clean projects stay readable after findings are added to text output.

Expected files

  • src/format.ts
  • tests/golden.test.mjs

Acceptance criteria

  • A clean fixture says Findings: 0 or equivalent.
  • It does not print empty findings or empty error sections.
  • Golden snapshot covers clean output.

Guardrails

  • One issue = one PR.
  • Add or update a behavior/golden test before changing behavior.
  • No runtime dependencies.
  • No new analyzer categories unless the issue explicitly says so.
  • Keep changes small; do not refactor src/analyze.ts broadly.

Verification

  • Run npm run build && npm test && git diff --check.
Suggested executor: Gemini 3.5 Flash. Wave: G1 — Text Output UX ## Goal Ensure clean projects stay readable after findings are added to text output. ## Expected files - `src/format.ts` - `tests/golden.test.mjs` ## Acceptance criteria - A clean fixture says `Findings: 0` or equivalent. - It does not print empty findings or empty error sections. - Golden snapshot covers clean output. ## Guardrails - One issue = one PR. - Add or update a behavior/golden test before changing behavior. - No runtime dependencies. - No new analyzer categories unless the issue explicitly says so. - Keep changes small; do not refactor `src/analyze.ts` broadly. ## Verification - Run `npm run build && npm test && git diff --check`.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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
pdurlej/fallow-ts#50
No description provided.