Add a global search, and stop the sidebar logo squeezing

`GET /api/v1/search/` hands the client one flat index of everything worth
jumping to — flows and the nodes inside them, dashboards and the widgets on
them, panels, secrets, modules, workers and alert channels — and cmdk matches
it in the browser, so results narrow while typing without a round trip per
keystroke. A node hit is the one thing no list endpoint could answer: it opens
its flow with that node in focus.

The panel is reached from **Search** above Documentation in the sidebar, or
⌘K anywhere. The flow canvas palette moves to ⌘P, being the narrower of the two.

The panels dialog gains an address (`/dashboards?panels`) so a panel hit has
somewhere to land, and the sidebar logo gets `shrink-0`: the rail's width
animates while the logo is already back, and a flex item short of room is
squeezed rather than clipped.
This commit is contained in:
2026-08-28 22:19:08 +02:00
parent 0fb864551e
commit 4a1ddcca3f
17 changed files with 642 additions and 39 deletions
+37
View File
@@ -2960,6 +2960,43 @@ export const RunRequestSchema = {
title: 'RunRequest'
} as const;
export const SearchEntrySchema = {
properties: {
category: {
type: 'string',
enum: ['flow', 'node', 'dashboard', 'widget', 'panel', 'secret', 'module', 'worker', 'alert'],
title: 'Category'
},
name: {
type: 'string',
title: 'Name'
},
title: {
type: 'string',
title: 'Title',
default: ''
},
parent: {
type: 'string',
title: 'Parent',
default: ''
},
kind: {
type: 'string',
title: 'Kind',
default: ''
}
},
type: 'object',
required: ['category', 'name'],
title: 'SearchEntry',
description: `One thing somebody might be looking for.
Deliberately not a route: where a category lands is the frontend's business,
and it already owns the router. This says what the thing is and what it is
called, which is all the matching needs.`
} as const;
export const SecretNamesSchema = {
properties: {
data: {
File diff suppressed because one or more lines are too long
+19
View File
@@ -1052,6 +1052,23 @@ export type RunRequest = {
};
};
/**
* One thing somebody might be looking for.
*
* Deliberately not a route: where a category lands is the frontend's business,
* and it already owns the router. This says what the thing is and what it is
* called, which is all the matching needs.
*/
export type SearchEntry = {
category: 'flow' | 'node' | 'dashboard' | 'widget' | 'panel' | 'secret' | 'module' | 'worker' | 'alert';
name: string;
title?: string;
parent?: string;
kind?: string;
};
export type category = 'flow' | 'node' | 'dashboard' | 'widget' | 'panel' | 'secret' | 'module' | 'worker' | 'alert';
export type SecretNames = {
data: Array<(string)>;
count: number;
@@ -1830,6 +1847,8 @@ export type RunsCompareMetricData = {
export type RunsCompareMetricResponse = (SeriesAnswer);
export type SearchReadSearchIndexResponse = (Array<SearchEntry>);
export type SecretsReadSecretsResponse = (SecretNames);
export type SecretsSaveSecretData = {