Skip to content

[Workspace] Add an accessible active-workspace selector #114

Open

Description

@mohit-nagaraj

Context

Parent: #112
Blocked by: #113

The dashboard currently has no explicit workspace context. Workspace-scoped
environment and application requests therefore have no safe source for their
workspaceId.

Outcome

The dashboard exposes an accessible active-workspace selector whose state can
be consumed by later workspace-scoped UI flows.

Scope

  • Add a focused workspace store using the typed client from the dependency.
  • Track workspaces, activeWorkspaceId, loading state, and a safe error state.
  • Auto-select only when exactly one workspace is available.
  • Require an explicit choice when multiple workspaces are available.
  • Clear an invalid selection after the workspace list changes.
  • Clear workspace state when authentication is removed so one signed-in user
    cannot inherit another user's selection.
  • Render the selector in the existing dashboard layout without resizing or
    overlapping navigation.
  • Cover loading, zero, one, multiple, failed-load, selection, and sign-out reset
    behavior with focused tests.

Out Of Scope

  • Persisting the selection across accounts or browser sessions.
  • Creating, renaming, deleting, or inviting members to a workspace.
  • Role-management UI.
  • Environment/application requests.
  • Mobile navigation redesign.
  • Core changes.

Acceptance Criteria

  • One workspace is selected automatically only when it is unambiguous.
  • Multiple workspaces require a deliberate user selection.
  • Empty and error states are distinguishable and accessible.
  • A failed request is not represented as an empty successful list.
  • Signing out clears workspace data and selection.
  • Keyboard users can open and change the selector.
  • Existing dashboard navigation still works at desktop and mobile widths.

Verification

  • Run focused store and component tests.
  • Run npm run type-check.
  • Run the relevant lint command.
  • Include desktop and mobile screenshots in the PR.

Dependencies

Complete #113 first.

Documentation And Observability

No public documentation change is expected. User-facing errors should state
that workspace loading failed and offer a retry without exposing raw backend
details.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/layoutUI layout/navigationarea/testingTesting, quality assurance, validationarea/uiNext.js frontend (components, pages, styling)good first issueGood for newcomerskind/integrationConnecting frontend with backendpriority/highsize/sSmall task (0.5 day)sprint/nextNext sprint planned items

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions