SurfSense/surfsense_web/zero/schema/automations.ts
Anish Sarkar a8c1fb660d feat(rename): complete searchSpace to workspace transition across frontend and backend
- Introduced a comprehensive specification for renaming `searchSpace` to `workspace` in `surfsense_web` and `surfsense_desktop`, ensuring all TypeScript identifiers, React props, and local data structures are updated.
- Implemented migration shims for persisted local state to prevent data loss during the transition.
- Updated observability metrics and IPC channels to reflect the new naming convention.
- Removed legacy `active-search-space` module and replaced it with `active-workspace` to maintain consistency.
- Ensured no behavioral changes or data loss for users during the renaming process.
2026-07-06 15:12:40 +05:30

25 lines
897 B
TypeScript

import { json, number, string, table } from "@rocicorp/zero";
export const automationTable = table("automations")
.columns({
id: number(),
workspaceId: number().from("workspace_id"),
})
.primaryKey("id");
// Thin live row: status + per-step progress only. Heavy fields
// (definition_snapshot, inputs, output, artifacts, error) stay on REST
// (`GET /automations/{id}/runs/{run_id}`) and load on detail expand.
// Mirrors the publication shape in migration 148.
export const automationRunTable = table("automation_runs")
.columns({
id: number(),
automationId: number().from("automation_id"),
triggerId: number().optional().from("trigger_id"),
status: string(),
stepResults: json().from("step_results"),
startedAt: number().optional().from("started_at"),
finishedAt: number().optional().from("finished_at"),
createdAt: number().from("created_at"),
})
.primaryKey("id");