Skip to content

chore(tui): delete the unused session footer component - #154

Merged
quickbeard merged 1 commit into
mainfrom
remove-dead-footer
Aug 2, 2026
Merged

quickbeard merged 1 commit into
mainfrom
remove-dead-footer

Conversation

@quickbeard

Copy link
Copy Markdown
Owner

What

Deletes packages/tui/src/routes/session/footer.tsx.

The file exported a Footer component — cwd, pending-permission count, LSP count, MCP count, /status — but nothing imports it. It is unreferenced in this fork and in upstream/dev, so it renders nowhere and never has in CoDev Code.

Everything it drew is already covered by the two footers that do render:

  • feature-plugins/sidebar/footer.tsx — cwd:branch plus the editor-context label
  • feature-plugins/home/footer.tsx — directory, MCP count, /status, version

Pending permissions surface through PermissionPrompt above the prompt, and LSP/MCP status through the sidebar panels.

Why

An unreferenced third copy of the status line invites edits to a component that never renders — a footer change made there would silently do nothing.

Notes

  • DIVERGENCES.md gets a row for the deletion (upstream file), with re-delete guidance for the next sync.
  • No CHANGELOG.md entry: nothing user-facing changes, since the component never rendered.
  • bun typecheck passes from packages/tui.

🤖 Generated with Claude Code

`routes/session/footer.tsx` exported a `Footer` (cwd, permission count,
LSP/MCP counts, `/status`) that nothing imports — it is unreferenced
upstream as well. The surfaces it rendered now live in the sidebar footer
(cwd:branch, editor-context label) and the home footer (dir, MCP,
`/status`, version).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@quickbeard
quickbeard merged commit d4fa9ed into main Aug 2, 2026
0 of 5 checks passed
@quickbeard
quickbeard deleted the remove-dead-footer branch August 2, 2026 10:35
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.

1 participant