@formicoidea/labre-framework-ddd-event-storming 0.32.0 → 0.33.0

package/dist/toolbar/senior-button.d.ts

@@ -2,5 +2,6 @@ import { DddSeniorButtonBase } from '@formicoidea/labre-ddd-shared';
 export declare class EdgelessDddEventStormingSeniorButton extends DddSeniorButtonBase {
     protected menuTag: "edgeless-ddd-event-storming-menu";
     protected label: string;
+    protected labelKey: string;
     protected icon: import("lit-html").TemplateResult<2>;
 }

package/dist/toolbar/senior-button.js

@@ -4,6 +4,7 @@ export class EdgelessDddEventStormingSeniorButton extends DddSeniorButtonBase {
         super(...arguments);
         this.menuTag = 'edgeless-ddd-event-storming-menu';
         this.label = 'Event Storming';
+        this.labelKey = 'com.labre.framework.ddd-event-storming';
         this.icon = eventStormingToolbarIcon;
     }
 }

package/dist/toolbar/senior-tool.js

@@ -3,6 +3,7 @@ import { html } from 'lit';
 /** Independent senior tool — Event Storming. */
 export const eventStormingSeniorTool = SeniorToolExtension('ddd-event-storming', ({ block }) => ({
     name: 'Event Storming',
+    labelKey: 'com.labre.framework.ddd-event-storming',
     content: html `<edgeless-ddd-event-storming-senior-button
       .edgeless=${block}
     ></edgeless-ddd-event-storming-senior-button>`,

package/dist/translations.d.ts

@@ -1,12 +1,14 @@
 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 Event Storming 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
- * core manifest could not restate them even if it wanted to. The
- * contribution therefore ships WITH the framework: in the bundled
- * distribution `@formicoidea/labre-framework-ddd-event-storming` carries it, and a host
+ * concrete keys exist nowhere but in the declarations themselves and the core
+ * manifest could not restate them even if it wanted to. The contribution
+ * therefore ships WITH the framework: in the bundled distribution
+ * `@formicoidea/labre-framework-ddd-event-storming` carries it, and a host
  * composes it into its catalogue exactly as it already composes
  * `eventStormingCommands` into the command registry. See
  * `packages/affine/all/src/translations.ts`.

package/dist/translations.js

@@ -1,15 +1,22 @@
-import { commandTranslationEntries, } from '@formicoidea/labre-core/std';
+import { collectTranslationKeys, commandTranslationEntries, mergeTranslationEntries, } from '@formicoidea/labre-core/std';
+import { EVENT_STORMING_BACKGROUND } from './background.js';
 import { eventStormingCommands } from './commands.js';
+import { EVENT_STORMING_NUDGES } from './nudges.js';
+import { EVENT_STORMING_PROFILES } from './profiles.js';
+import { EVENT_STORMING_ROLES } from './roles.js';
+import { EVENT_STORMING_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 Event Storming 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
- * core manifest could not restate them even if it wanted to. The
- * contribution therefore ships WITH the framework: in the bundled
- * distribution `@formicoidea/labre-framework-ddd-event-storming` carries it, and a host
+ * concrete keys exist nowhere but in the declarations themselves and the core
+ * manifest could not restate them even if it wanted to. The contribution
+ * therefore ships WITH the framework: in the bundled distribution
+ * `@formicoidea/labre-framework-ddd-event-storming` carries it, and a host
  * composes it into its catalogue exactly as it already composes
  * `eventStormingCommands` into the command registry. See
  * `packages/affine/all/src/translations.ts`.
  */
-export const eventStormingTranslationEntries = commandTranslationEntries(eventStormingCommands);
+export const eventStormingTranslationEntries = mergeTranslationEntries(commandTranslationEntries(eventStormingCommands), collectTranslationKeys('role', EVENT_STORMING_ROLES), collectTranslationKeys('background', EVENT_STORMING_BACKGROUND), collectTranslationKeys('rule', EVENT_STORMING_RULES), collectTranslationKeys('nudge', EVENT_STORMING_NUDGES), collectTranslationKeys('profile', EVENT_STORMING_PROFILES));

package/dist/view.d.ts

@@ -1,6 +1,22 @@
 import { type ViewExtensionContext, ViewExtensionProvider } from '@formicoidea/labre-core/ext-loader';
 /**
- * Event Storming — independently flag-gated (`ddd-event-storming`).
+ * Event Storming rendering — ALWAYS registered, independent of any flag.
+ * Disabling `ddd-event-storming` hides only the creation tooling (see
+ * {@link DddEventStormingViewExtension}); boards already stormed must still
+ * paint, stay selectable, stay movable and keep their contextual toolbar. See
+ * `docs/adr/0009`.
+ */
+export declare class DddEventStormingRenderViewExtension extends ViewExtensionProvider {
+    name: string;
+    setup(context: ViewExtensionContext): void;
+}
+/**
+ * Event Storming creation tooling — independently flag-gated
+ * (`ddd-event-storming`): the senior toolbar button, its palette and the
+ * validation rules, profiles and quality nudges. Both halves are tooling: a
+ * board stormed while the flag was on keeps rendering when it goes off, it just
+ * stops being checked — and the profile it was put on stays written, unread,
+ * until the flag comes back.
  *
  * Note: its Templates-panel category is registered by the aggregate package's
  * {@link DddTemplatesViewExtension} (gated by `ddd-templates`), so templates

package/dist/view.js

@@ -1,10 +1,54 @@
+import { QualityNudgeExtension, validationToolbarConfig, ValidationProfileExtension, ValidationRuleExtension, } from '@formicoidea/labre-core/blocks/surface';
 import { ViewExtensionProvider, } from '@formicoidea/labre-core/ext-loader';
-import { CommandExtension } from '@formicoidea/labre-core/std';
-import { eventStormingCommandIcons, eventStormingCommands, } from './commands.js';
+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 { eventStormingCommandIcons, eventStormingCommands } from './commands.js';
 import { eventStormingEffects } from './effects.js';
+import { EventStormingRendererExtension } from './element-renderer.js';
+import { EventStormingInteraction, EventStormingView } from './element-view.js';
+import { EVENT_STORMING_NUDGES } from './nudges.js';
+import { EVENT_STORMING_PROFILES } from './profiles.js';
+import { EVENT_STORMING_ROLES } from './roles.js';
+import { EVENT_STORMING_RULES } from './rules.js';
+import { eventStormingBoardToolbarExtension } from './toolbar/board-config.js';
 import { eventStormingSeniorTool } from './toolbar/senior-tool.js';
 /**
- * Event Storming — independently flag-gated (`ddd-event-storming`).
+ * Event Storming rendering — ALWAYS registered, independent of any flag.
+ * Disabling `ddd-event-storming` hides only the creation tooling (see
+ * {@link DddEventStormingViewExtension}); boards already stormed must still
+ * paint, stay selectable, stay movable and keep their contextual toolbar. See
+ * `docs/adr/0009`.
+ */
+export class DddEventStormingRenderViewExtension extends ViewExtensionProvider {
+    constructor() {
+        super(...arguments);
+        this.name = 'affine-ddd-event-storming-render-gfx';
+    }
+    setup(context) {
+        super.setup(context);
+        context.register(EventStormingView);
+        context.register(EventStormingRendererExtension);
+        // The role VOCABULARY, always on. A role is written in the DOCUMENT, not in
+        // the tooling: the direction reveal of a typed flow, the inversion command
+        // and the toolbar entry that must not lie about one all read this, and they
+        // have to keep working on a board stormed while the flag was on and opened
+        // while it is off (`docs/adr/0009`, `docs/adr/0010`). The rules that JUDGE
+        // those roles stay in the flag-gated extension below.
+        context.register(RoleVocabularyExtension(EVENT_STORMING_ROLES));
+        if (this.isEdgeless(context.scope)) {
+            context.register(EventStormingInteraction);
+            context.register(eventStormingBoardToolbarExtension);
+        }
+    }
+}
+/**
+ * Event Storming creation tooling — independently flag-gated
+ * (`ddd-event-storming`): the senior toolbar button, its palette and the
+ * validation rules, profiles and quality nudges. Both halves are tooling: a
+ * board stormed while the flag was on keeps rendering when it goes off, it just
+ * stops being checked — and the profile it was put on stays written, unread,
+ * until the flag comes back.
  *
  * Note: its Templates-panel category is registered by the aggregate package's
  * {@link DddTemplatesViewExtension} (gated by `ddd-templates`), so templates
@@ -22,6 +66,20 @@ export class DddEventStormingViewExtension extends ViewExtensionProvider {
     setup(context) {
         super.setup(context);
         if (this.isEdgeless(context.scope)) {
+            context.register(ValidationRuleExtension(EVENT_STORMING_RULES));
+            context.register(ValidationProfileExtension(EVENT_STORMING_PROFILES));
+            context.register(QualityNudgeExtension(EVENT_STORMING_NUDGES));
+            // The Validation dropdown on a selected board's contextual toolbar. A
+            // SECOND module on the same element, through the `custom:` flavour slot:
+            // `eventStormingBoardToolbarExtension` is registered always-on because a
+            // stored board must keep its resize toggle, while choosing how hard to
+            // check it is tooling and belongs here. The config names no framework —
+            // it reads roles and profiles — so it is the very same object Wardley
+            // registers on its own flavour.
+            context.register(ToolbarModuleExtension({
+                id: BlockFlavourIdentifier('custom:affine:surface:eventStorming'),
+                config: validationToolbarConfig,
+            }));
             context.register(eventStormingSeniorTool);
             context.register(CommandExtension(eventStormingCommands, eventStormingCommandIcons));
         }

package/package.json

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