@aranzatech/diagrams-bpmn 0.2.13 → 0.2.15

package/dist/layout/index.d.cts

@@ -1,31 +1,42 @@
 import { LayoutResult, LayoutOptions } from '@aranzatech/diagrams-core/types';
 export { applyLayoutResultToDiagram } from '@aranzatech/diagrams-core/layout';
-import { d as BpmnRFNode, c as BpmnRFEdge } from '../types-s2_VvPGf.cjs';
+import { d as BpmnRFNode, c as BpmnRFEdge } from '../types-jIDz306Y.cjs';
 import { BpmnDiagramState } from '../modeling/index.cjs';
 import '@xyflow/react';
-import '../types-Dfrt0wVs.cjs';
+import '../types-y-ZbX-ff.cjs';
 import '@aranzatech/diagrams-core';
 import '@aranzatech/diagrams-core/serialization';
-import '../catalog-BiLXVn-2.cjs';
+import '../catalog-xOMF2ifW.cjs';
 
 /**
  * ELK-based auto-layout for BPMN diagrams.
  *
- * Direction policy — always LEFT-TO-RIGHT to match screen anatomy:
+ * Spacing philosophy: fixed, generous values that scale consistently
+ * regardless of diagram size. "Air" between elements is not waste —
+ * it is what makes the flow readable to the human eye.
+ *
+ * Direction policy:
  * - Root: RIGHT — free nodes and pools flow LR on the canvas.
- * - Pool that contains Lanes: DOWN internally so lanes stack top-to-bottom
- *   (standard horizontal-pool anatomy); the pool itself is still placed LR.
- * - Pool without lanes, Lane, SubProcess, Transaction, AdHoc: RIGHT — content
- *   flows left-to-right inside the container.
- * - All edges get ORTHOGONAL routing in a single INCLUDE_CHILDREN pass so
- *   cross-pool and cross-lane edges are routed correctly.
- * - Containers auto-resize to fit their children.
+ * - Pool with Lanes: DOWN internally so lanes stack top-to-bottom;
+ *   the pool itself is placed LR on the canvas.
+ * - Lane / SubProcess / Pool-without-lanes: RIGHT — content flows LR.
+ * - Each container runs its own INCLUDE_CHILDREN pass (per-container
+ *   hierarchyHandling) so cross-lane edges are routed correctly without
+ *   the global RIGHT direction forcing Lane containers sideways.
+ * - Root uses INHERIT so each pool is laid out independently.
+ * - Post-processing equalises Lane widths within each Pool so all Lanes
+ *   span the full Pool width.
  */
 declare function bpmnElkLayout(nodes: BpmnRFNode[], edges: BpmnRFEdge[]): Promise<{
     nodes: BpmnRFNode[];
     edges: BpmnRFEdge[];
 }>;
 
+declare function bpmnCustomLayout(nodes: BpmnRFNode[], edges: BpmnRFEdge[]): Promise<{
+    nodes: BpmnRFNode[];
+    edges: BpmnRFEdge[];
+}>;
+
 /**
  * Dagre layout pre-configured for BPMN diagrams.
  * Uses BPMN-specific node sizes (events 52×52, gateways 64×64, tasks 192×64, etc.)
@@ -38,4 +49,4 @@ declare function bpmnDagreLayout(nodes: BpmnRFNode[], edges: BpmnRFEdge[], optio
  */
 declare function applyBpmnLayoutResult(state: BpmnDiagramState, result: LayoutResult): BpmnDiagramState;
 
-export { applyBpmnLayoutResult, bpmnDagreLayout, bpmnElkLayout };
+export { applyBpmnLayoutResult, bpmnCustomLayout, bpmnDagreLayout, bpmnElkLayout };

package/dist/layout/index.d.ts

@@ -1,31 +1,42 @@
 import { LayoutResult, LayoutOptions } from '@aranzatech/diagrams-core/types';
 export { applyLayoutResultToDiagram } from '@aranzatech/diagrams-core/layout';
-import { d as BpmnRFNode, c as BpmnRFEdge } from '../types-rEfHsPr5.js';
+import { d as BpmnRFNode, c as BpmnRFEdge } from '../types-DG5yPKld.js';
 import { BpmnDiagramState } from '../modeling/index.js';
 import '@xyflow/react';
-import '../types-Dfrt0wVs.js';
+import '../types-y-ZbX-ff.js';
 import '@aranzatech/diagrams-core';
 import '@aranzatech/diagrams-core/serialization';
-import '../catalog-Di2nzGs9.js';
+import '../catalog-CK3_4cOb.js';
 
 /**
  * ELK-based auto-layout for BPMN diagrams.
  *
- * Direction policy — always LEFT-TO-RIGHT to match screen anatomy:
+ * Spacing philosophy: fixed, generous values that scale consistently
+ * regardless of diagram size. "Air" between elements is not waste —
+ * it is what makes the flow readable to the human eye.
+ *
+ * Direction policy:
  * - Root: RIGHT — free nodes and pools flow LR on the canvas.
- * - Pool that contains Lanes: DOWN internally so lanes stack top-to-bottom
- *   (standard horizontal-pool anatomy); the pool itself is still placed LR.
- * - Pool without lanes, Lane, SubProcess, Transaction, AdHoc: RIGHT — content
- *   flows left-to-right inside the container.
- * - All edges get ORTHOGONAL routing in a single INCLUDE_CHILDREN pass so
- *   cross-pool and cross-lane edges are routed correctly.
- * - Containers auto-resize to fit their children.
+ * - Pool with Lanes: DOWN internally so lanes stack top-to-bottom;
+ *   the pool itself is placed LR on the canvas.
+ * - Lane / SubProcess / Pool-without-lanes: RIGHT — content flows LR.
+ * - Each container runs its own INCLUDE_CHILDREN pass (per-container
+ *   hierarchyHandling) so cross-lane edges are routed correctly without
+ *   the global RIGHT direction forcing Lane containers sideways.
+ * - Root uses INHERIT so each pool is laid out independently.
+ * - Post-processing equalises Lane widths within each Pool so all Lanes
+ *   span the full Pool width.
  */
 declare function bpmnElkLayout(nodes: BpmnRFNode[], edges: BpmnRFEdge[]): Promise<{
     nodes: BpmnRFNode[];
     edges: BpmnRFEdge[];
 }>;
 
+declare function bpmnCustomLayout(nodes: BpmnRFNode[], edges: BpmnRFEdge[]): Promise<{
+    nodes: BpmnRFNode[];
+    edges: BpmnRFEdge[];
+}>;
+
 /**
  * Dagre layout pre-configured for BPMN diagrams.
  * Uses BPMN-specific node sizes (events 52×52, gateways 64×64, tasks 192×64, etc.)
@@ -38,4 +49,4 @@ declare function bpmnDagreLayout(nodes: BpmnRFNode[], edges: BpmnRFEdge[], optio
  */
 declare function applyBpmnLayoutResult(state: BpmnDiagramState, result: LayoutResult): BpmnDiagramState;
 
-export { applyBpmnLayoutResult, bpmnDagreLayout, bpmnElkLayout };
+export { applyBpmnLayoutResult, bpmnCustomLayout, bpmnDagreLayout, bpmnElkLayout };