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:
@@ -1,5 +1,5 @@
|
||||
import { expect, type Page, test } from "@playwright/test"
|
||||
import { api, apiPage, deleteAll } from "./utils/api"
|
||||
import { api, apiPage, createDashboard, deleteAll } from "./utils/api"
|
||||
|
||||
/**
|
||||
* The dashboard editor's quiet failures.
|
||||
@@ -41,7 +41,7 @@ test.describe.configure({ mode: "serial" })
|
||||
|
||||
test.beforeAll(async ({ browser }) => {
|
||||
const page = await apiPage(browser)
|
||||
await api(page, `/dashboards/${dashboardName}`, { method: "POST" })
|
||||
await createDashboard(page, { name: dashboardName })
|
||||
// The working copy, which is what a new dashboard may be: the editor reads
|
||||
// the draft, so the setup writes one rather than publishing.
|
||||
const dashboard = await (
|
||||
|
||||
Reference in New Issue
Block a user