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:
@@ -97,14 +97,14 @@ export function DashboardPalette({
|
||||
<CommandGroup heading="Dashboards">
|
||||
{dashboards.map((dashboard) => (
|
||||
<CommandItem
|
||||
key={dashboard.name}
|
||||
key={dashboard.id}
|
||||
value={`dashboard ${dashboard.name} ${dashboard.title}`}
|
||||
onSelect={() =>
|
||||
close(() =>
|
||||
// Editing a neighbour is the same job, as on the rail.
|
||||
navigate({
|
||||
to: "/dashboards/$name",
|
||||
params: { name: dashboard.name },
|
||||
to: "/dashboards/$id",
|
||||
params: { id: dashboard.id! },
|
||||
search: { edit: true },
|
||||
}),
|
||||
)
|
||||
|
||||
Reference in New Issue
Block a user