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
+15 -18
View File
@@ -1,5 +1,5 @@
import { expect, test } from "@playwright/test"
import { api, apiPage, deleteAll } from "./utils/api"
import { api, apiPage, createFlow, deleteAll } from "./utils/api"
/**
* What a message carrying a dictionary looks like in a panel four hundred
@@ -21,23 +21,20 @@ test.describe.configure({ mode: "serial" })
test.beforeAll(async ({ browser }) => {
const page = await apiPage(browser)
await api(page, `/flows/${flowName}`, {
method: "PUT",
data: {
name: flowName,
title: "Values",
version: 1,
nodes: [
{
id: "emit",
type: "python",
provides: [
{ name: "shape", dtype: "record" },
{ name: "label", dtype: "str" },
],
},
],
},
await createFlow(page, {
name: flowName,
title: "Values",
version: 1,
nodes: [
{
id: "emit",
type: "python",
provides: [
{ name: "shape", dtype: "record" },
{ name: "label", dtype: "str" },
],
},
],
})
// Saving writes a draft and moves the version on, so publish what is
// actually there rather than what it was a moment ago.