Implementation: How to extend CrossToolSync to all platform builder tools?
Documentation for Sessions
⚙️ Implementation: How to extend CrossToolSync to all platform builder tools?
📋 Decision Context
Question:
How to extend CrossToolSync to all platform builder tools?
Task: Extend CrossToolSync to all platform builder tools
🎯 Decision Made
Chosen:
Add to each tool individually
Options Considered:
- Add to each tool individually
- Create a base class with CrossToolSync
- Use a mixin pattern
💭 Reasoning
Each tool has unique data operations (create/update/delete) that need specific broadcast calls. Adding CrossToolSyncService injection and appropriate broadcast calls to each tool's component ensures proper event types and payloads. Tools updated: space-map-lib, universe-map, modularity-lib, editor-workspace. All now broadcast node:create, node:update, node:delete events for bidirectional sync.
📁 Files Involved
libs/libs-structural/space-map-lib/src/lib/state/space-map.state.tslibs/libs-structural/universe-map/src/lib/components/universe-map/universe-map.component.tslibs/libs-structural/modularity-lib/src/lib/components/module-workbench/module-workbench.component.tslibs/libs-structural/editor-web-lib/src/lib/components/editor-workspace/editor-workspace.component.ts
🔗 Related
- Decision ID:
dev_1767824615870_5po44c3 - Session: 22
- Workspace: editor2
Auto-generated by MCP Smart Consolidation