@zenwave360/lsp-js 0.1.0-next.17.2 → 0.1.0-next.19.1

package/README.md

@@ -55,6 +55,7 @@ hover, definition, references, document symbols and formatting. `capabilities.ex
 - `organizeModes`: `true` when `zenwave/organizeZflServices` accepts `mode` (`full`, the default, or `additive`).
 - `savedPositions`: `true` when `zenwave/eventFlowViews` accepts `positions` and answers `savedPositions`.
 - `flowVariants`: `true` when `zenwave/eventFlowViews` accepts its optional `variant` parameter and returns variants.
+- `flowLanes`: `string[]`, the `lanes` values `zenwave/eventFlowViews` accepts (`none`, `systems`, `services`).
 
 ## Custom requests
 
@@ -63,7 +64,7 @@ hover, definition, references, document symbols and formatting. `capabilities.ex
 | `zenwave/hierarchy` | `{ uri }` | hierarchy nodes `{ id, label, kind, language, sourceUri, sourceRange, children, relatedResources, uiHints, viewNodeIds }[]` |
 | `zenwave/forwardReferences`, `zenwave/reverseReferences` | `{ uri, semanticId }` | navigation targets |
 | `zenwave/organizeZflServices` | `{ uri, mode?: "full" \| "additive" }` | the reorganised ZFL text, or `null` |
-| `zenwave/eventFlowViews` | `{ textDocument: { uri }, variant?: string, positions?: { [nodeId]: { x, y } } }` | `{ flowGraph, serviceGraph, variants: [{ id, title }], savedPositions? }`: dsl-kotlin's laid-out flow and full service view models, each with its `schema` (`zfl.eventflow.view@1`, `zfl.services.view@1`); `variant` selects the flow graph only. `positions` (full diagram only; ignored with `variant`) replaces automatic layout when every node has a finite position, and then `savedPositions` is `{ applied: true }`; otherwise the layout is automatic and it is `{ applied: false, reason: "missing-nodes" \| "invalid", missing: [nodeId] }`. A non-object `positions` is `-32602` |
+| `zenwave/eventFlowViews` | `{ textDocument: { uri }, variant?: string, positions?: { [nodeId]: { x, y } }, lanes?: "none" \| "systems" \| "services" }` | `{ flowGraph, serviceGraph, variants: [{ id, title }], savedPositions?, lanes? }`: dsl-kotlin's laid-out flow and full service view models, each with its `schema` (`zfl.eventflow.view@1`, `zfl.services.view@1`); `variant` selects the flow graph only. `positions` (full diagram only; ignored with `variant`) replaces automatic layout when every node has a finite position, and then `savedPositions` is `{ applied: true }`; otherwise the layout is automatic and it is `{ applied: false, reason: "missing-nodes" \| "invalid", missing: [nodeId] }`. A non-object `positions` is `-32602`. `lanes` (absent is `none`) draws the flow graph, variants included, in full-width bands: `flowGraph.lanes` is `{ id, kind: "system" \| "service", label, system, x, y, width, height, order }[]` and each node has `lane` (a band id); the effective value is echoed as `lanes` when the request named it, and a value other than the three, or a non-string, is `-32602`. With `systems` or `services` the layout is always automatic: `positions` are not used and `savedPositions` is `{ applied: false, reason: "lanes", missing: [] }` |
 | `zenwave/preview` | `{ textDocument: { uri }, mode?: "docs" \| "diagrams", sequenceRenderMode?: "SEPARATE_VARIANTS" \| "ALT_BLOCKS" \| "AUTO" }` | `{ representations: { id, title, format: "MARKDOWN" \| "MERMAID" \| "HTML", content, group? }[], defaultRepresentationId }` |
 | `zenwave/symbolAt` | `{ textDocument: { uri }, position: { line, character } }` | `{ uri, semanticId, range? }`, the input of the two reference requests, or `null` when nothing is declared or referenced there |