Close the 039 REST-binding and pipeline-view gaps found in the audit: the scenario API client was never imported and pipeline views were not bound to any page. T054/T056 - dashboard-testing.ts gains compileScenario/validateScenario/ resolveScenario (requestApi POST); WorkspaceModel.compileFromRest / validateFromRest / resolveFromRest give an agent-free REST preview path; DashboardScenarioWorkspaceModel.rest.test.ts (3 tests). T055 - capture/vlm/disposition REST surface already landed on backend (038 T057/T058); EvidencePanel autonomous binding deferred to follow. T057 - DashboardDetailModel.loadVerificationRuns() + VerificationHistoryList bound on /dashboards/[id], consuming 037 T081 GET /verification/history; DashboardDetailModel.test.ts = 67 passed. T058 (verify action) intentionally left open: VerificationRunRequest needs a repository_id which dashboard metadata does not expose, and there is no PREPROD deployment page in the frontend. Documented as a blocker in tasks.md. Verification: 79 vitest passed (REST + detail model + api), vite build OK; eslint clean for changed code (pre-existing URLSearchParams lint on old line left untouched).
Superset Tools Frontend (SvelteKit)
This is the frontend for the Superset Tools application, built with SvelteKit in SPA mode.
Development
-
Install dependencies:
npm install -
Run development server:
npm run devThe frontend will be available at
http://localhost:5173. It is configured to proxy API requests tohttp://localhost:8000.
Production Build
-
Build the static SPA:
npm run buildThis generates a static SPA in the
build/directory. -
Serve with Backend: The Python backend is configured to serve the files from
frontend/build/. Ensure the backend is running:cd ../backend python src/app.py
Architecture
- Routing: File-based routing in
src/routes/. - Layouts: Shared UI in
src/routes/+layout.svelte. - Data Loading:
loadfunctions in+page.tsfor efficient data fetching. - API Client: Centralized API logic in
src/lib/api.js. - Styling: Tailwind CSS.