propagate transaction changes until all changes are propagated

[georghinkel]

Summary by MergeMonkey

• Fixes & Patches:
  • Fixes incomplete change propagation in transactions by looping until all changes are processed

[mergemonkeyhq]

Walkthrough

When a transaction commits, the system now uses a while loop instead of a single if-check to propagate changes. This ensures that if processing one node's changes triggers changes in other nodes, those subsequent changes are also processed until both change collections are empty.

Changes

Files	Summary
Transaction Change Propagation Fix Expressions/Expressions/Execution/ExecutionEngine.cs Expressions/Expressions.history	Fixes transaction commit to loop through all pending changes instead of processing only once, ensuring dependent node changes are fully propagated

Sequence Diagram

sequenceDiagram
    participant C as CommitTransaction()
    participant L as changeListener
    participant N as changedNodes
    loop while L or N have changes
        C->>C: Collect all changed nodes
        C->>L: Process changeListener notifications
        C->>N: Process changedNodes updates
    end
    C-->>C: Transaction committed when all changes propagated

Loading

Dig Deeper With Commands

• /review <file-path> <function-optional>
• /chat <file-path> "<question>"
• /roast <file-path>

Runs only when explicitly triggered.