Mastercard / flow

Testing framework

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Builder debug

therealryan opened this issue · comments

The lack of guardrails around flow construction is intentional, but the downside is that how a message ends up with the data that it does can be arbitrarily complicated: answering a "Why does this field have that value?" can be difficult.

It'd be nice to offer a debug mode where the state of a message can be monitored and tracked as updates are applied. The source of message updates should be identified.