@formicoidea/labre-framework-ddd-context-map 0.35.0 → 0.37.0

package/dist/commands.js

@@ -29,6 +29,7 @@ const SPECS = [
         // A NEW telemetry value, and the only one in this file: every other entry
         // below keeps the `element` string it has emitted since ADR 0008.
         element: 'board',
+        board: true,
         icon: boardSwatch,
         run: std => createContextMapBoard(std.get(GfxControllerIdentifier)),
     },
@@ -79,6 +80,10 @@ export const contextMapCommands = SPECS.map((spec, order) => ({
     defaultKeys: { mac: [], other: [] },
     availability: 'always',
     run: spec.run,
-    telemetry: { framework: 'ddd-context-map', element: spec.element },
+    telemetry: {
+        framework: 'ddd-context-map',
+        element: spec.element,
+        board: spec.board,
+    },
 }));
 export const contextMapCommandIcons = Object.fromEntries(SPECS.map(spec => [spec.iconKey, spec.icon]));

package/dist/index.d.ts

@@ -9,3 +9,4 @@ export { contextMapTemplateCategory } from './templates.js';
 export { contextMapSeniorTool } from './toolbar/senior-tool.js';
 export { EdgelessDddContextMapSeniorButton } from './toolbar/senior-button.js';
 export { DddContextMapRenderViewExtension, DddContextMapViewExtension, } from './view.js';
+export { CONTEXT_MAP_READING } from './reading.js';

package/dist/index.js

@@ -9,3 +9,4 @@ export { contextMapTemplateCategory } from './templates.js';
 export { contextMapSeniorTool } from './toolbar/senior-tool.js';
 export { EdgelessDddContextMapSeniorButton } from './toolbar/senior-button.js';
 export { DddContextMapRenderViewExtension, DddContextMapViewExtension, } from './view.js';
+export { CONTEXT_MAP_READING } from './reading.js';

package/dist/reading.d.ts

@@ -0,0 +1,36 @@
+import type { ReadingProfile } from '@formicoidea/labre-core/blocks/surface';
+/**
+ * What a Context Map lets the tool read of a bounded context (MF3, the reversed
+ * reading).
+ *
+ * DATA, like the rules and the profiles beside it: the engine
+ * (`@labre/affine-block-surface`) knows how to read a role and a typed edge — it
+ * knows nothing about context mapping. Everything below is already stated in
+ * `roles.ts` and is merely POINTED AT here.
+ *
+ * Registered from the FLAG-GATED view extension: reading a map is tooling, so a
+ * board whose flag is off keeps every element it has and simply stops being read
+ * (ADR 0009).
+ *
+ * ## One subject, and the board is not it
+ *
+ * `context-map:context` is the only artefact this notation places; the board is
+ * the FRAME and specialises nothing, exactly so that what is written about the
+ * contexts never falls on the card they sit on.
+ *
+ * ## The nine patterns are read through their parent
+ *
+ * `appliesTo` on the relation is `context-map:relationship`, and the nine DDD
+ * Crew patterns specialise it — so `roleIsA` reaches every one of them without
+ * this file naming a single pattern. The four SYMMETRIC ones (Partnership,
+ * Shared Kernel, Separate Ways, Big Ball of Mud) declare no `direction`, and the
+ * panel still lists them under whichever side the drawing put them on: that is
+ * not a claim about upstream and downstream, it is where the link happens to
+ * start. The asymmetry is the notation's, and `roles.ts` is where it is argued.
+ *
+ * ## No nature, no phase
+ *
+ * The framework ships no type-3 tag pack, and the board declares no zones a
+ * position could be read against.
+ */
+export declare const CONTEXT_MAP_READING: ReadingProfile;

package/dist/reading.js

@@ -0,0 +1,57 @@
+import { CONTEXT_MAP_ROLE, CONTEXT_MAP_ROLES } from './roles.js';
+/**
+ * What a Context Map lets the tool read of a bounded context (MF3, the reversed
+ * reading).
+ *
+ * DATA, like the rules and the profiles beside it: the engine
+ * (`@labre/affine-block-surface`) knows how to read a role and a typed edge — it
+ * knows nothing about context mapping. Everything below is already stated in
+ * `roles.ts` and is merely POINTED AT here.
+ *
+ * Registered from the FLAG-GATED view extension: reading a map is tooling, so a
+ * board whose flag is off keeps every element it has and simply stops being read
+ * (ADR 0009).
+ *
+ * ## One subject, and the board is not it
+ *
+ * `context-map:context` is the only artefact this notation places; the board is
+ * the FRAME and specialises nothing, exactly so that what is written about the
+ * contexts never falls on the card they sit on.
+ *
+ * ## The nine patterns are read through their parent
+ *
+ * `appliesTo` on the relation is `context-map:relationship`, and the nine DDD
+ * Crew patterns specialise it — so `roleIsA` reaches every one of them without
+ * this file naming a single pattern. The four SYMMETRIC ones (Partnership,
+ * Shared Kernel, Separate Ways, Big Ball of Mud) declare no `direction`, and the
+ * panel still lists them under whichever side the drawing put them on: that is
+ * not a claim about upstream and downstream, it is where the link happens to
+ * start. The asymmetry is the notation's, and `roles.ts` is where it is argued.
+ *
+ * ## No nature, no phase
+ *
+ * The framework ships no type-3 tag pack, and the board declares no zones a
+ * position could be read against.
+ */
+export const CONTEXT_MAP_READING = {
+    id: 'context-map',
+    framework: 'ddd-context-map',
+    roles: CONTEXT_MAP_ROLES,
+    appliesTo: CONTEXT_MAP_ROLE.context,
+    relation: {
+        edgeRole: CONTEXT_MAP_ROLE.relationship,
+        // The DDD Crew wording, verbatim, and the direction `roles.ts` declares:
+        // the SOURCE is the upstream context. So an edge leaving the subject names
+        // what is downstream of it, and one arriving names what it is downstream of.
+        sides: {
+            consumer: {
+                labelKey: 'com.labre.ddd-context-map.reading.relations.consumer',
+                labelFallback: 'Upstream',
+            },
+            supplier: {
+                labelKey: 'com.labre.ddd-context-map.reading.relations.supplier',
+                labelFallback: 'Downstream',
+            },
+        },
+    },
+};

package/dist/translations.js

@@ -3,6 +3,7 @@ import { CONTEXT_MAP_BACKGROUND } from './background.js';
 import { contextMapCommands } from './commands.js';
 import { CONTEXT_MAP_NUDGES } from './nudges.js';
 import { CONTEXT_MAP_PROFILES } from './profiles.js';
+import { CONTEXT_MAP_READING } from './reading.js';
 import { CONTEXT_MAP_ROLES } from './roles.js';
 import { CONTEXT_MAP_RULES } from './rules.js';
 /**
@@ -23,4 +24,9 @@ export const contextMapTranslationEntries = mergeTranslationEntries(commandTrans
 // registry names no framework category in the bundled distribution, so a
 // host that composed core's manifest alone drew translated entries under
 // English headers (#183).
-commandCategoryTranslationEntries(contextMapCommands), collectTranslationKeys('role', CONTEXT_MAP_ROLES), collectTranslationKeys('background', CONTEXT_MAP_BACKGROUND), collectTranslationKeys('rule', CONTEXT_MAP_RULES), collectTranslationKeys('nudge', CONTEXT_MAP_NUDGES), collectTranslationKeys('profile', CONTEXT_MAP_PROFILES));
+commandCategoryTranslationEntries(contextMapCommands), collectTranslationKeys('role', CONTEXT_MAP_ROLES), collectTranslationKeys('background', CONTEXT_MAP_BACKGROUND), collectTranslationKeys('rule', CONTEXT_MAP_RULES), collectTranslationKeys('nudge', CONTEXT_MAP_NUDGES), collectTranslationKeys('profile', CONTEXT_MAP_PROFILES), 
+// LAST, and the order is load-bearing: a reading profile carries the
+// framework's own `roles`, so walking it reaches every role key the `role`
+// line above already named. `mergeTranslationEntries` keeps the FIRST
+// occurrence, which is what makes each key report the source it comes from.
+collectTranslationKeys('reading', CONTEXT_MAP_READING));

package/dist/view.js

@@ -1,4 +1,4 @@
-import { QualityNudgeExtension, validationToolbarConfig, ValidationProfileExtension, ValidationRuleExtension, } from '@formicoidea/labre-core/blocks/surface';
+import { QualityNudgeExtension, ReadingProfileExtension, validationToolbarConfig, ValidationProfileExtension, ValidationRuleExtension, } from '@formicoidea/labre-core/blocks/surface';
 import { ViewExtensionProvider, } from '@formicoidea/labre-core/ext-loader';
 import { ToolbarModuleExtension } from '@formicoidea/labre-core/shared/services';
 import { BlockFlavourIdentifier, CommandExtension } from '@formicoidea/labre-core/std';
@@ -9,6 +9,7 @@ import { ContextMapRendererExtension } from './element-renderer.js';
 import { ContextMapInteraction, ContextMapView } from './element-view.js';
 import { CONTEXT_MAP_NUDGES } from './nudges.js';
 import { CONTEXT_MAP_PROFILES } from './profiles.js';
+import { CONTEXT_MAP_READING } from './reading.js';
 import { CONTEXT_MAP_ROLES } from './roles.js';
 import { CONTEXT_MAP_RULES } from './rules.js';
 import { contextMapBoardToolbarExtension } from './toolbar/board-config.js';
@@ -80,6 +81,12 @@ export class DddContextMapViewExtension extends ViewExtensionProvider {
                 id: BlockFlavourIdentifier('custom:affine:surface:contextMap'),
                 config: validationToolbarConfig,
             }));
+            // The reversed reading (MF3): what the map says about a bounded context,
+            // on demand. One declaration — the roles and the relationship edge, both
+            // already stated elsewhere in this framework. The CLICK that triggers it
+            // is registered once by the surface and gated by the presence of this
+            // profile, so it goes with the flag without either side naming the other.
+            context.register(ReadingProfileExtension(CONTEXT_MAP_READING));
             context.register(contextMapSeniorTool);
             context.register(CommandExtension(contextMapCommands, contextMapCommandIcons));
         }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@formicoidea/labre-framework-ddd-context-map",
   "description": "Labre ddd-context-map framework for @formicoidea/labre-core.",
-  "version": "0.35.0",
+  "version": "0.37.0",
   "type": "module",
   "sideEffects": false,
   "author": "lajola",
@@ -31,8 +31,8 @@
     "dist"
   ],
   "dependencies": {
-    "@formicoidea/labre-core": "0.35.0",
-    "@formicoidea/labre-ddd-shared": "0.35.0",
+    "@formicoidea/labre-core": "0.37.0",
+    "@formicoidea/labre-ddd-shared": "0.37.0",
     "lit": "^3.2.0"
   }
 }