Skip to content

Keep Tasks plain output records on one TSV row #220

Closed

Description

@itsjeremyjohnson

This issue was generated by AI for maintainer triage.

Idea

Use the shared plain-output sanitizer for task titles and task-list titles in all existing Tasks list tables.

Evidence

Task item listing, due-date listing, and task-list listing write API-provided titles directly into tab-separated rows. Titles are user-controlled and these paths do not use the shared field sanitizer before plain-mode output.

Why it matters

Tabs or line breaks in a task title can create extra rows or columns, making otherwise documented plain output unsafe for reliable parsing.

Initial acceptance checks

  • Task and task-list titles containing tabs, newlines, or carriage returns never alter the physical row count or column count in --plain output.
  • JSON and human-readable output retain the original title values.

Scope boundaries

  • Do not change task ordering, due-date selection, or plain table schemas.

Activity

  1. itsjeremyjohnson commented on Aug 16, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    This was generated by AI during triage.

    Agent Brief

    Category: bug
    Summary: Preserve Tasks plain-output row and column boundaries for titles.

    Current behavior:
    Task-item listing, due-date listing, and task-list listing write user-controlled titles directly into tab-separated rows. These paths bypass the shared plain-field sanitizer, so tabs or line breaks can inject columns or records. No historical change covers these callers.

    Desired behavior:
    All existing Tasks list tables should sanitize task and task-list titles in plain mode, keeping one API object per physical row and retaining current schemas. JSON and default human-readable output should keep the original title values.

    Key interfaces:

    • Task-item, due-date, and task-list row emitters — use the shared mode-aware table-row contract.
    • The shared plain-field sanitizer — handle tabs, LF, CR, and CRLF.

    Acceptance criteria:

    • Task titles cannot alter the physical row or column count in task-item plain output.
    • Task titles cannot alter the due-date listing schema.
    • Task-list titles cannot alter the task-list listing schema.
    • JSON and default human-readable output retain original titles.
    • Tests cover all affected tables and each supported control-character form.

    Out of scope:

    • Task ordering, due-date selection, or table schema changes.
  2. added
    ready-for-agentFully specified and ready for an agent
    and removed
    needs-triageMaintainer needs to evaluate this issue
    on Aug 16, 2026
  3. itsjeremyjohnson commented on Oct 12, 2026

    @itsjeremyjohnson
    CollaboratorAuthor

    Closing as obsolete (GitHub sweep 2026-10-12). This issue describes behavior of the gog CLI command layer. The CLI was removed from this repository in 91336b7 (#269, "refactor(mcp): retire CLI distribution and rewrite server docs"), which deleted cmd/gog and all of internal/cmd; main now builds only gog-mcp, and none of the symbols this issue names exist on main (checked at bf17220). There is no code path left to fix here. A fix to the installed v0.10.0 binary would mean restoring the CLI, which is a separate decision. If the same gap appears in a gog-mcp operation, please file it against the MCP surface.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions