Architecture: How should visual page-builder widgets connect to module CRU...

Documentation for Sessions

🏗️ Architecture: How should visual page-builder widgets connect to module CRU...

Date: 2026-01-22
Time: 15:32:23 UTC
Session: editor2-57.8
Agent: angular
Confidence: 92%
Status: ✅ Documented

📋 Decision Context

Question:

How should visual page-builder widgets connect to module CRUD operations?

Task: Session 57.2: Widget-Module CRUD Binding Architecture

🎯 Decision Made

Chosen:

Declarative WidgetDataConfig with WidgetModuleBinding and WidgetEventBinding types, resolved at runtime by WidgetDataBindingService

Options Considered:

Embed CRUD logic directly in widgets
Create declarative widget-module binding types with runtime resolver
Props drilling from parent containers

💭 Reasoning

Keeps page-builder widgets visual-only (aligned with Session 56 decision that editor2 UI is superior). Data operations are configured declaratively via JSON-serializable bindings, not coded into widgets. Runtime resolver handles refresh policies, input/output mappings (JSONPath), caching, and error handling. AI can generate these binding configs alongside widget code.

📁 Files Involved

libs/libs-foundational/core-models/src/lib/types/widget-data-binding.types.ts
libs/libs-structural/page-builder/src/lib/services/widget-data-binding.service.ts

🔗 Related

Decision ID: dev_1769095943872_o08t1jx
Session: 57
Workspace: editor2

Auto-generated by MCP Smart Consolidation