Skip to content

vscode: migrate Status view from sidebar to Codev panel tab #815

Description

@amrmelsayed

Problem

The Status view (packages/vscode/src/views/status.ts) lives in the Codev sidebar today, occupying a row for what's essentially a single piece of connection state (connected / disconnected to Tower) plus a codev.reconnect action. The sidebar's row-per-view real estate isn't justified by the content. Moving Status to the panel groups it with the other secondary surfaces (Recently Closed, Team) and frees a sidebar slot.

The status-bar option (where this kind of state typically lives) was considered and explicitly deferred ("Not now") in favor of the panel placement; this issue documents that decision.

Proposed behavior

Migrate the existing codev.status view from the codev (sidebar) container to the new codevPanel (panel) container introduced in #812. No data, rendering, or interaction changes — same provider, same row(s), same codev.reconnect view-title action.

Implementation

  1. In packages/vscode/package.json, move the codev.status view entry from contributes.views.codev to contributes.views.codevPanel.
  2. codev.reconnect in view/title is keyed by view == codev.status — no when-clause change needed.
  3. Smoke-test that the connection-state row updates on connect / disconnect events after the move.

Acceptance criteria

  • codev.status registered under viewsContainers.panel.codevPanel, not under activitybar.codev.
  • Status tab no longer appears in the Codev sidebar.
  • Connection-state row appears in the Codev panel area, fully functional.
  • codev.reconnect action still fires correctly from the panel-side view title.
  • No regression to other Codev views (sidebar or panel).

Depends on

Out of scope

Activity

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

Metadata

Metadata

Assignees

Labels

area/vscodeArea: VS Code extensionprojectNew project or feature

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions