Repository navigation
Open
Labels
area/apiREST endpointsREST endpointsarea/testingTesting, quality assurance, validationTesting, quality assurance, validationarea/uiNext.js frontend (components, pages, styling)Next.js frontend (components, pages, styling)good first issueGood for newcomersGood for newcomerskind/integrationConnecting frontend with backendConnecting frontend with backendpriority/highsize/xsExtra small task (1-2 hours)Extra small task (1-2 hours)sprint/nextNext sprint planned itemsNext sprint planned items
Description
Context
Parent: #112
Core already exposes documented Beta read contracts for workspaces,
environments, and applications, but UI has no TypeScript types or service
methods for them. Components should not hand-build these URLs or invent
response shapes.
Core contract references:
GET /v1/api/workspacesGET /v1/api/workspaces/{workspaceId}GET /v1/api/workspaces/{workspaceId}/environmentsGET /v1/api/workspaces/{workspaceId}/applicationsGET /v1/api/workspaces/{workspaceId}/applications/{applicationId}
Outcome
UI has one small, typed, tested read client matching the existing Core
workspace, environment, application, and pagination contracts.
Scope
- Add TypeScript types for workspace, environment, application, and page-info
responses using the exact Core JSON field names. - Add service methods to list workspaces, list environments for a workspace,
list applications for a workspace, and get one application. - Support
cursorandlimiton list calls. - Support
environmentIdandincludeArchivedon application lists. - Omit optional query parameters when they are not provided.
- Use the existing shared Axios client so bearer authentication, runtime base
URL, timeout, and 401 handling remain centralized. - Add focused unit tests for paths, query serialization, response shapes, and
rejected requests.
Out Of Scope
- Zustand state or React components.
- Create, update, archive, membership, artifact, release, plan, or approval calls.
- Changes to Core or the OpenAPI contract.
- Generated API clients or a new HTTP dependency.
- Retrying or transforming authorization errors.
Acceptance Criteria
- Types match Core's
{ items, pageInfo }list envelope and camelCase fields. - Workspace-scoped paths use the supplied workspace ID.
- Application filters are serialized only when supplied.
- The existing API client remains the only bearer-token owner.
- HTTP failures reject to the caller without being converted into empty lists.
- Tests use dummy IDs and make no network requests.
Verification
- Run the focused service test.
- Run
npm run type-check. - Run the relevant lint command.
Dependencies
Core #115 and #116 are complete. No new Core implementation is required.
Documentation And Observability
No public documentation change is expected. Keep Beta-contract naming in one
frontend module so later contract changes are easy to locate.
Metadata
Metadata
Assignees
Labels
area/apiREST endpointsREST endpointsarea/testingTesting, quality assurance, validationTesting, quality assurance, validationarea/uiNext.js frontend (components, pages, styling)Next.js frontend (components, pages, styling)good first issueGood for newcomersGood for newcomerskind/integrationConnecting frontend with backendConnecting frontend with backendpriority/highsize/xsExtra small task (1-2 hours)Extra small task (1-2 hours)sprint/nextNext sprint planned itemsNext sprint planned items
Activity
ankitv909 commentedon Sep 13, 2026
Hi! I’d like to work on this issue. I’ll keep the change scoped to the typed Beta read client described here: workspace/environment/application response types, cursor/filter query serialization through the existing shared Axios client, and focused Vitest coverage for paths, optional params, response shapes, and rejection behavior. I’ll verify with the focused tests, type-check, and lint before opening the PR.