The site promises simulated inputs and mocked sensor values, and nothing in the app was that. A run already is: the values are the caller's, the state is the run's own namespace, and nothing it computes reaches the live flow. What was missing was a screen to do it from, and the draft flag being honoured. `/runs/new` is a flow, a field per declared input, a seed and Run; `/runs` stays the log. A comma-separated list in a number field expands into the grid `fluksio sweep --param` builds and goes to the sweep route, so launching one no longer needs a terminal. Only numbers split: a comma in a string is content, and one in JSON is syntax. `RunCreate.draft` was validated at submit and dropped before the run executed, so "try the working copy" ran the published one. `Run.draft` is a column now, the driver reads the same copy the submit checked, and a retry carries it. `FlowSummary.mode` came with it so the rail can say which flows are batch before one is picked. Also here: a Retry button on a finished run, which the route has always had and the UI never did, and parameter cells truncated to their column with the full value on hover.
27 lines
797 B
TypeScript
27 lines
797 B
TypeScript
import { createFileRoute, useNavigate } from "@tanstack/react-router"
|
|
|
|
import { NewRun } from "@/components/Runs/NewRun"
|
|
|
|
export const Route = createFileRoute("/_layout/runs/new")({
|
|
component: Page,
|
|
// Which flow is being run is the address, so a link opens the form on it —
|
|
// the same way the history screen's filter is a link.
|
|
validateSearch: (search: Record<string, unknown>): { flow?: string } => ({
|
|
flow:
|
|
typeof search.flow === "string" && search.flow ? search.flow : undefined,
|
|
}),
|
|
head: () => ({ meta: [{ title: "New run - Fluksio" }] }),
|
|
})
|
|
|
|
function Page() {
|
|
const { flow } = Route.useSearch()
|
|
const navigate = useNavigate()
|
|
|
|
return (
|
|
<NewRun
|
|
flow={flow}
|
|
onPick={(next) => navigate({ to: "/runs/new", search: { flow: next } })}
|
|
/>
|
|
)
|
|
}
|