v0.8.2
Diagnostic hints for code node input errors
- Proxy-based diagnostics: code nodes now show exactly which keys are available in
input,trigger, andstatewhen accessing a missing property — no more guessing where data lives - Enhanced error context: runtime errors include available keys hint when "Cannot read property" occurs
- Improved
flow_rundescription: documents the state model (trigger,env, node outputs) and how code nodes receiveinputvsstate
Example error (before)
Cannot read properties of undefined (reading 'email_to')
Example error (after)
'email_to' is not a key in input. Input keys: [client, order_number].
Did you mean state.trigger.email_to? It exists in trigger.