treege 3.0.0-beta.60 → 3.0.0-beta.62

package/dist/editor/features/TreegeEditor/forms/SensitiveHeaderWarning.d.ts

@@ -1,6 +1,6 @@
-import { HttpHeader } from '../../../../shared/types/node';
+import { KeyValueEntry } from '../../../../shared/utils/httpRecord';
 interface SensitiveHeaderWarningProps {
-    headers?: HttpHeader[];
+    headers?: KeyValueEntry[];
 }
 /**
  * Inline alert shown when a field-level header carries credentials (e.g. an

package/dist/editor/features/TreegeEditor/panel/ActionsPanel.d.ts

@@ -1,12 +1,12 @@
 import { ExtraMenuItem } from '../../../types/editor';
-import { Flow, HttpHeader } from '../../../../shared/types/node';
+import { Flow, HttpHeaders } from '../../../../shared/types/node';
 export interface ActionsPanelProps {
     onExportJson?: (data: Flow) => void;
     onSave?: (data: Flow) => void;
     extraMenuItems?: ExtraMenuItem[];
-    onAuthorize?: (headers: HttpHeader[]) => void;
-    headers?: HttpHeader[];
-    onHeadersChange?: (headers: HttpHeader[]) => void;
+    onAuthorize?: (headers: HttpHeaders) => void;
+    headers?: HttpHeaders;
+    onHeadersChange?: (headers: HttpHeaders) => void;
 }
 declare const ActionsPanel: ({ onExportJson, onSave, extraMenuItems, onAuthorize, headers, onHeadersChange }: ActionsPanelProps) => import("react/jsx-runtime").JSX.Element;
 export default ActionsPanel;

package/dist/editor/hooks/useKeyValueRows.d.ts

@@ -0,0 +1,15 @@
+import { KeyValueEntry } from '../../shared/utils/httpRecord';
+/**
+ * Bridges an editable list of key/value rows with a persisted
+ * `Record<string, string>` (headers, query params…).
+ *
+ * Records can't hold a half-typed row (an empty key, or two rows mid-edit), so
+ * the rows are the local source of truth while editing. Every mutation is
+ * serialized back to a record — empty keys dropped, last wins on duplicates —
+ * and pushed up via `onChange`. The rows reseed from `record` only when it
+ * changes from the outside (a different node, a static↔api toggle), never in
+ * response to our own emit, so adding a blank row doesn't immediately vanish.
+ * The reseed happens during render (React's recommended pattern) rather than in
+ * an effect, so there's no extra commit/flash.
+ */
+export declare const useKeyValueRows: (record: Record<string, string> | undefined, onChange: (record: Record<string, string>) => void) => readonly [KeyValueEntry[], (rows: KeyValueEntry[]) => void];

package/dist/editor/types/editor.d.ts

@@ -2,7 +2,7 @@ import { Edge, Node } from '@xyflow/react';
 import { ReactNode } from 'react';
 import { AIConfig } from './ai';
 import { OpenApiDocument } from './openapi';
-import { Flow, HttpHeader } from '../../shared/types/node';
+import { Flow, HttpHeaders } from '../../shared/types/node';
 export interface ExtraMenuItem {
     /**
      * Label displayed in the menu item.
@@ -99,26 +99,20 @@ export interface TreegeEditorProps {
      * route resolution; otherwise this value is the base.
      */
     baseUrl?: string;
-    /**
-     * @deprecated Use `baseUrl` instead — it now covers OpenAPI route resolution
-     * and the general runtime base. Kept as an alias for backward compatibility;
-     * `baseUrl` wins when both are set.
-     */
-    openApiBaseUrl?: string;
     /**
      * Global HTTP headers applied to in-editor requests (e.g. the "Detect
      * fields" button in `OptionsSourceForm`). Pass the same value you give to
      * `TreegeRenderer` so editor-time previews use the same auth and headers
      * that the runtime form will use.
      */
-    headers?: HttpHeader[];
+    headers?: HttpHeaders;
     /**
      * Called when the user submits the Authorize dialog. Receives the resulting
      * HTTP headers (`Authorization`, API key headers…). The consumer is expected
      * to forward those headers to `TreegeRenderer` (or `TreegeRendererProvider`)
      * via its `headers` prop so every request issued by the form is authenticated.
      */
-    onAuthorize?: (headers: HttpHeader[]) => void;
+    onAuthorize?: (headers: HttpHeaders) => void;
     /**
      * Called whenever the user edits the global headers via the editor's
      * built-in "Global headers" dialog. The component is controlled — the
@@ -126,5 +120,5 @@ export interface TreegeEditorProps {
      * the new list back via the `headers` prop, so every editor-time and
      * runtime request reflects the change.
      */
-    onHeadersChange?: (headers: HttpHeader[]) => void;
+    onHeadersChange?: (headers: HttpHeaders) => void;
 }

package/dist/editor/utils/sensitiveHeaders.d.ts

@@ -1,8 +1,13 @@
-import { Flow, HttpHeader } from '../../shared/types/node';
+import { Flow } from '../../shared/types/node';
+import { KeyValueEntry } from '../../shared/utils/httpRecord';
 /** True when a header key is known to carry credentials/secrets. */
 export declare const isSensitiveHeaderKey: (key: string) => boolean;
-/** True when the list contains a sensitive header with a non-empty value. */
-export declare const hasSensitiveHeader: (headers?: HttpHeader[]) => boolean;
+/**
+ * True when the editor rows contain a sensitive header with a non-empty value.
+ * Operates on the form's working rows (which may still hold empty keys) rather
+ * than the serialized record, so the warning shows as soon as the user types.
+ */
+export declare const hasSensitiveHeader: (headers?: KeyValueEntry[]) => boolean;
 /**
  * Returns a copy of the flow with all credential-bearing field-level headers
  * removed from every node's httpConfig/optionsSource/submitConfig, plus the