Phase 5: Block Configuration System - Progress Update

Status: PARTIAL COMPLETE (5.1 & 5.4 DONE)
Date: October 24, 2025
Sprint: Phase 5 - Block Configuration System

Completed Tasks

✅ Phase 5.1: Enhanced Block Data Model (COMPLETE)

File Modified: libs/singularity-lib/src/lib/types/logic-builder.types.ts

Added comprehensive config property to LogicBlock interface:

config?: {
  // Input configuration
  inputs?: {
    [inputName: string]: {
      type: 'variable' | 'constant' | 'connection';
      value?: any;  // For constants
      variableName?: string;  // For variable references ($a)
      connectionId?: string;  // For port connections
      defaultValue?: any;
    };
  };
  
  // Output configuration
  outputs?: {
    [outputName: string]: {
      variableName?: string;  // Where to store result
    };
  };
  
  // Block-specific settings
  settings?: {
    operation?: string;  // For Calculate: 'add', 'subtract', etc.
    [key: string]: any;
  };
  
  // UI/Visual settings
  ui?: {
    color?: string;
    icon?: string;
    collapsed?: boolean;
  };
};

Impact:

• Blocks can now be fully configured by users
• All configuration stored as JSON (shareable)
• Backward compatible (config is optional)

✅ Phase 5.4: Update Execution Engine (COMPLETE)

File Modified: libs/singularity-lib/src/lib/services/logic-execution-engine.service.ts

New Methods Added:

1. resolveInputsFromConfig()

   • Resolves block inputs from config structure
   • Supports: constant values, variable references, port connections
   • Logs resolution for debugging

2. storeOutputsFromConfig()

   • Stores execution results in configured output variables
   • Maps outputs to user-named variables

3. Updated executeFunctionBlock()

   • Checks for block.config first
   • Falls back to block.properties for backward compatibility
   • Uses resolved inputs from config
   • Stores results in configured output variables

4. Updated executeActionBlock()

   • Reads operation from config.settings
   • Resolves inputs from config
   • Merges into properties for existing action handlers
   • Stores outputs after execution

Example Usage:

// Block with config
const block: LogicBlock = {
  id: 'calc_001',
  name: 'Add Numbers',
  type: 'function',
  config: {
    inputs: {
      a: { type: 'variable', variableName: 'inputA' },
      b: { type: 'constant', value: 10 }
    },
    settings: {
      operation: 'add'
    },
    outputs: {
      result: { variableName: 'total' }
    }
  }
  // ... other fields
};

// Execution automatically resolves:
// - Reads $inputA from context
// - Uses constant 10 for b
// - Executes add operation
// - Stores result in 'total' variable

Logging Output:

📝 [Config] Input "a" = 5 (from variable: inputA)
📝 [Config] Input "b" = 10 (constant)
🔧 [Function] Using block.config for inputs
🧮 [Calculate] 5 + 10 = 15
💾 [Config] Output "result" stored in variable: total = 15

Remaining Phase 5 Tasks

Pending: Phase 5.2 - Block Configuration Modal Component

New Files to Create:

• libs/singularity-lib/src/lib/components/logic-builder/components/block-config-modal/block-config-modal.component.ts
• libs/singularity-lib/src/lib/components/logic-builder/components/block-config-modal/block-config-modal.component.html
• libs/singularity-lib/src/lib/components/logic-builder/components/block-config-modal/block-config-modal.component.scss

Features:

• Modal opens on double-click block
• Tabs: Inputs, Outputs, Settings, Appearance
• Input configuration UI (variable/constant/connection selector)
• Output variable naming
• Settings panel (operation selectors, etc.)
• Color picker for appearance
• Save button updates block.config via singularityService

Pending: Phase 5.3 - Inline Quick Config

File to Modify:

• libs/singularity-lib/src/lib/components/logic-builder/components/block-card/block-card.component.ts

Features:

• Inline operation selector (add/subtract/multiply buttons)
• Inline input editors
• Live result preview badge
• Click to expand full config modal

Technical Notes

Backward Compatibility

All config-aware code checks for block.config first and falls back to block.properties:

if (block.config?.inputs) {
  // Use new config system
  args = this.resolveInputsFromConfig(block.config.inputs, context);
} else {
  // Fallback to old properties
  args = block.properties?.['arguments'] || {};
}

This ensures:

• Existing flows continue to work
• No migration required
• Users can gradually adopt new config system

Data Structure

Config is optional and stored directly in LogicBlock:

interface LogicBlock {
  // ... existing fields ...
  config?: { /* ... */ };  // Optional
}

Persists through:

• Flash Persistence (autoFlashState)
• GgStorage (IndexedDB)
• Export/Import (JSON)

Execution Flow

User edits block config (Phase 5.2 - pending)
    ↓
Config saved to block.config via singularityService
    ↓
Block persists to storage (autoFlashState)
    ↓
Execution engine reads block.config
    ↓
Resolves inputs (variables, constants, connections)
    ↓
Executes block logic
    ↓
Stores result in configured output variable

Next Steps

1. Phase 5.2: Create Block Configuration Modal Component
2. Phase 5.3: Add Inline Quick Config to Block Cards
3. Phase 6: AI Integration (can be done in parallel)
4. Phase 7: Export/Import System

Success Metrics

✅ Completed:

• Block data model enhanced
• Execution engine reads from config
• Backward compatible
• Zero linting errors

🔄 In Progress:

• UI components for configuration

⏳ Pending:

• Block configuration modal
• Inline quick config
• User testing

Last Updated: October 24, 2025
Files Modified: 2
Lines Added: ~150
Linting Errors: 0