Frontend addresses flows and dashboards by id: routes /flows/$flowId, /dashboards/$id and /view/$id, query keys, saves, lists, device pickers, search, brain and endpoint links and generated results dashboards go by id, while live values, issues, pauses and message names keep the key; tabs take the title from the document; creating uses POST and opens the issued id; the flow and dashboard panels show key and id with a copy button and a served HTTP or WebSocket node shows its hook URL under the flow id; specs create by POST and ids.spec.ts exercises issued ids

This commit is contained in:
2026-11-02 19:57:43 +01:00
parent fd637e0f1e
commit fa15522cb0
65 changed files with 1380 additions and 784 deletions
@@ -49,11 +49,14 @@ export type InspectedEdge = {
export function EdgeInspector({
edge,
flow,
flowId,
onClose,
onUnbind,
}: {
edge: InspectedEdge | null
/** The flow's key, which its messages are named under. */
flow: string
flowId: string
onClose: () => void
onUnbind: (message: string) => void
}) {
@@ -64,7 +67,7 @@ export function EdgeInspector({
const replay = useMutation({
mutationFn: (value: unknown) =>
FlowsService.triggerNode({
flowId: flow,
flowId,
nodeId: edge?.sourceId ?? "",
requestBody: { values: { [edge?.message ?? ""]: value } },
}),
@@ -145,6 +148,7 @@ export function EdgeInspector({
<div className="mt-2">
<MessageSparkline
flow={flow}
flowId={flowId}
name={displayName(flow, edge.message)}
/>
</div>