@zwishing/emap 0.1.0

package/dist/map/worker-routing.d.ts

@@ -0,0 +1,40 @@
+/**
+ * Pull every leading `-NAME` token out of a CLI command string. Used by
+ * the router to decide on the basis of the command FAMILY rather than a
+ * single hard-coded keyword.
+ *
+ * Returns names in source order; e.g. `'-target X -dissolve foo'` →
+ * `['target', 'dissolve']`.
+ */
+export declare function parseCommandHeads(cmd: string): string[];
+/**
+ * Decide whether `cmd` should run on a worker.
+ *
+ * Routing precedence:
+ *   - `mode === false` → always main thread.
+ *   - `mode === true`  → always worker (assuming a pool exists).
+ *   - `mode === 'auto'`:
+ *     - command is entirely cheap (every `-X` head in CHEAP_COMMANDS)
+ *       → main thread regardless of vertex count.
+ *     - any expensive head present → worker when
+ *       `vertexCount >= threshold * EXPENSIVE_THRESHOLD_RATIO`.
+ *     - otherwise → worker when `vertexCount >= threshold`.
+ */
+export declare function shouldUseWorker(cmd: string, vertexCount: number, mode: boolean | 'auto', threshold: number): boolean;
+/**
+ * Same routing decision as {@link shouldUseWorker} but consuming a
+ * pre-extracted heads array. Used by the PR-4b parsed-command path
+ * (`commands.map(c => c.name)`) so it doesn't have to round-trip through
+ * a CLI string just to make a routing call.
+ */
+export declare function shouldUseWorkerForHeads(heads: string[], vertexCount: number, mode: boolean | 'auto', threshold: number): boolean;
+/** Custom routing-decision callback users can supply via `MapOptions`. */
+export type WorkerRoutingFn = (info: {
+    cmd: string;
+    heads: string[];
+    vertexCount: number;
+    mode: boolean | 'auto';
+    threshold: number;
+    /** Default decision the engine would have made; user may return it as-is. */
+    defaultDecision: boolean;
+}) => boolean;