Open
Description
At present, the print logs are directly printed using standard Go's fmt.Println. Ideally these print logs should be captured per transition. So, we would be able to replay the logs in the error trace when debugging.
Where we associate the logs depends on the context where the logs are printed
- Action: All the logs printed should be associated with the transition/
*Link. - Transition assertions: The Print statements within the transition should be associated with the transition
*Link. - Safety and liveness assertions: These should be associated with the state
*Node.