@formicoidea/labre-framework-bpmn 0.32.0 → 0.33.0

package/dist/translations.d.ts

@@ -1,6 +1,8 @@
 import { type TranslationKeyManifestEntry } from '@formicoidea/labre-core/std';
 /**
- * THIS framework's contribution to the translation-key manifest.
+ * THIS framework's contribution to the translation-key manifest — every
+ * `com.labre.*` key BPMN can hand to `TranslationProvider.t`, derived from the
+ * very declarations the editor registers (never restated).
  *
  * Its command labels and descriptions are built from a TEMPLATE, so the
  * concrete keys exist nowhere but in the declarations themselves and the

package/dist/translations.js

@@ -1,7 +1,12 @@
-import { commandTranslationEntries, } from '@formicoidea/labre-core/std';
+import { collectTranslationKeys, commandTranslationEntries, mergeTranslationEntries, } from '@formicoidea/labre-core/std';
 import { bpmnCommands } from './commands.js';
+import { BPMN_PROFILES } from './profiles.js';
+import { BPMN_ROLES } from './roles.js';
+import { BPMN_RULES } from './rules.js';
 /**
- * THIS framework's contribution to the translation-key manifest.
+ * THIS framework's contribution to the translation-key manifest — every
+ * `com.labre.*` key BPMN can hand to `TranslationProvider.t`, derived from the
+ * very declarations the editor registers (never restated).
  *
  * Its command labels and descriptions are built from a TEMPLATE, so the
  * concrete keys exist nowhere but in the declarations themselves and the
@@ -12,4 +17,4 @@ import { bpmnCommands } from './commands.js';
  * `bpmnCommands` into the command registry. See
  * `packages/affine/all/src/translations.ts`.
  */
-export const bpmnTranslationEntries = commandTranslationEntries(bpmnCommands);
+export const bpmnTranslationEntries = mergeTranslationEntries(commandTranslationEntries(bpmnCommands), collectTranslationKeys('role', BPMN_ROLES), collectTranslationKeys('rule', BPMN_RULES), collectTranslationKeys('profile', BPMN_PROFILES));

package/dist/view.d.ts

@@ -10,8 +10,12 @@ export declare class BpmnRenderViewExtension extends ViewExtensionProvider {
     setup(context: ViewExtensionContext): void;
 }
 /**
- * BPMN creation tooling — flag-gated (`bpmn`): the senior toolbar button and
- * its templates category.
+ * BPMN creation tooling — flag-gated (`bpmn`): the senior toolbar button, its
+ * templates category, the validation rules and profiles, and the interchange
+ * capabilities. All of it is tooling: a process drawn while the flag was on
+ * keeps rendering when it goes off, it just stops being checked — the profile
+ * its pool was put on stays written, unread, until the flag comes back, and so
+ * does anything an import wrote (`docs/adr/0009`, `docs/adr/0012`).
  */
 export declare class BpmnViewExtension extends ViewExtensionProvider {
     name: string;

package/dist/view.js

@@ -1,11 +1,20 @@
+import { FrameworkBackgroundInteractionExtension, InterchangeExtension, morphToolbarConfig, ValidationProfileExtension, ValidationRuleExtension, validationToolbarConfig, } from '@formicoidea/labre-core/blocks/surface';
 import { ViewExtensionProvider, } from '@formicoidea/labre-core/ext-loader';
 import { extendTemplateCategory } from '@formicoidea/labre-core/gfx/template';
-import { CommandExtension } from '@formicoidea/labre-core/std';
+import { ToolbarModuleExtension } from '@formicoidea/labre-core/shared/services';
+import { BlockFlavourIdentifier, CommandExtension } from '@formicoidea/labre-core/std';
+import { RoleVocabularyExtension } from '@formicoidea/labre-core/std/gfx';
+import { BPMN_POOL_BACKGROUND } from './background.js';
 import { bpmnCommandIcons, bpmnCommands } from './commands.js';
 import { effects } from './effects.js';
+import { BPMN_INTERCHANGE } from './interchange.js';
+import { BPMN_MORPH_SPEC } from './morph.js';
+import { BPMN_PROFILES } from './profiles.js';
+import { BPMN_ROLES } from './roles.js';
+import { BPMN_RULES } from './rules.js';
 import { bpmnTemplateCategory } from './templates/index.js';
 import { BpmnPoolRendererExtension } from './element-renderer.js';
-import { BpmnPoolInteraction, BpmnPoolView } from './element-view.js';
+import { BpmnPoolView } from './element-view.js';
 import { BpmnNodeRendererExtension } from './node/node-renderer.js';
 import { BpmnNodeView } from './node/node-view.js';
 import { bpmnPoolToolbarExtension } from './toolbar/config.js';
@@ -27,15 +36,28 @@ export class BpmnRenderViewExtension extends ViewExtensionProvider {
         context.register(BpmnPoolRendererExtension);
         context.register(BpmnNodeView);
         context.register(BpmnNodeRendererExtension);
+        // The role VOCABULARY, always on. A role is written in the document, not in
+        // the tooling: the direction reveal of the sequence flow, the inversion
+        // command and the toolbar entry that must not lie about a typed edge all
+        // read this, and they have to keep working on a process drawn while the flag
+        // was on and opened while it is off (`docs/adr/0009`, `docs/adr/0010`).
+        context.register(RoleVocabularyExtension(BPMN_ROLES));
         if (this.isEdgeless(context.scope)) {
-            context.register(BpmnPoolInteraction);
+            // Resize gating, driven by the declaration like every other framework
+            // background: the handles stay hidden until `resizeEnabled` says
+            // otherwise, and the toolbar toggle is what writes it.
+            context.register(FrameworkBackgroundInteractionExtension(BPMN_POOL_BACKGROUND));
             context.register(bpmnPoolToolbarExtension);
         }
     }
 }
 /**
- * BPMN creation tooling — flag-gated (`bpmn`): the senior toolbar button and
- * its templates category.
+ * BPMN creation tooling — flag-gated (`bpmn`): the senior toolbar button, its
+ * templates category, the validation rules and profiles, and the interchange
+ * capabilities. All of it is tooling: a process drawn while the flag was on
+ * keeps rendering when it goes off, it just stops being checked — the profile
+ * its pool was put on stays written, unread, until the flag comes back, and so
+ * does anything an import wrote (`docs/adr/0009`, `docs/adr/0012`).
  */
 export class BpmnViewExtension extends ViewExtensionProvider {
     constructor() {
@@ -51,6 +73,47 @@ export class BpmnViewExtension extends ViewExtensionProvider {
     setup(context) {
         super.setup(context);
         if (this.isEdgeless(context.scope)) {
+            context.register(ValidationRuleExtension(BPMN_RULES));
+            context.register(ValidationProfileExtension(BPMN_PROFILES));
+            // Reading and writing `.bpmn` files, declared rather than assumed
+            // (`docs/adr/0012`). Tooling like the rest of this class: with the flag
+            // off there is nothing to export WITH, while a board a past import wrote
+            // keeps every element and every byte it was given (`docs/adr/0009`).
+            context.register(InterchangeExtension(BPMN_INTERCHANGE));
+            // The Validation dropdown on a selected pool's contextual toolbar. A
+            // SECOND module on the same element, through the `custom:` flavour slot,
+            // exactly as wardley and the context map register it on theirs:
+            // `bpmnPoolToolbarExtension` is registered always-on because a stored pool
+            // must keep its lanes and its resize toggle, while choosing how hard to
+            // check the process is tooling and belongs here. The config names no
+            // framework — it reads roles and profiles — so it is the very same object
+            // the other two register.
+            context.register(ToolbarModuleExtension({
+                id: BlockFlavourIdentifier('custom:affine:surface:bpmnPool'),
+                config: validationToolbarConfig,
+            }));
+            // The "Change type" dropdown on a selected NODE's contextual toolbar —
+            // the generic module, parameterized by BPMN's own families table.
+            //
+            // `affine:surface:bpmnNode` is a FREE slot, and class inheritance has
+            // nothing to do with it: `renderToolbar` merges by flavour KEY — the
+            // element's own, its `custom:` twin and the `affine:surface:*` wildcards
+            // — so `shapeToolbarExtension`, which binds `affine:surface:shape`, never
+            // reaches a bpmn node however much of `ShapeElementModel` the class
+            // inherits. Nothing claimed this key before, so the registration is purely
+            // additive: it joins the wildcard entries (tags, validation) that a node
+            // already gets, and a second module claiming the same key would throw
+            // `DuplicateServiceDefinitionError` before the editor finished setting up.
+            //
+            // Registered HERE, in the flag-gated half, because a morph is TOOLING: a
+            // node drawn while the flag was on keeps its kind, its role, its glyph
+            // and its place in every rule when the flag goes off — it just stops
+            // being something the toolbar offers to say more precisely
+            // (`docs/adr/0009`).
+            context.register(ToolbarModuleExtension({
+                id: BlockFlavourIdentifier('affine:surface:bpmnNode'),
+                config: morphToolbarConfig(BPMN_MORPH_SPEC),
+            }));
             context.register(bpmnSeniorTool);
             context.register(CommandExtension(bpmnCommands, bpmnCommandIcons));
         }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@formicoidea/labre-framework-bpmn",
   "description": "Labre bpmn framework for @formicoidea/labre-core.",
-  "version": "0.32.0",
+  "version": "0.33.0",
   "type": "module",
   "sideEffects": false,
   "author": "lajola",
@@ -27,7 +27,7 @@
     "dist"
   ],
   "dependencies": {
-    "@formicoidea/labre-core": "0.32.0",
+    "@formicoidea/labre-core": "0.33.0",
     "lit": "^3.2.0"
   }
 }